. Special Instructions None. Regards, Simon Coulter. A cleanup thread runs once an hour to determine whether a QZRCSRVS job is still being used by a Job Monitor. Tuto tabulku serverů lze použít k vyhledání toho, jak jsou servery, serverové úlohy, popisy úloh a subsystémy vzájemně mapovány. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). period of time to end. 5. It determines if the job was used at least twice within the maximum job monitor interval length. IBM ® i Support for Windows Network Neighborhood (IBM i NetServer) is an IBM i function that enables Windows 2000, Windows XP, Windows Server 2003, and Windows Vista clients to access IBM i sharedQZLSSERVER is IBM Net Server. Verify the QZLSSERVER job is active using WRKACTJOB JOB(QZLSSERVER) at the 5250 Emulation screen prompt. Ouch. 活動ジョブ処理（wrkactjobコマンド）でジョブの状況を確認したら、サブシステムqserverの配下にqzlsfilet とqzlsserverがありません。 strtcpsvr *netsvrを実行したら、cpib683で理由コード13が出てしまいます。 何が原因なのでしょうか。Verify that the system has started the QZLSSERVER job within QSERVER. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. The Start Server (QZSLSTRS) and End Server (QZLSENDS) APIs start and end the server. To display the contents of the history log QHST, complete the following steps: Type DSPLOG (the Display Log command) on the command line. misc. Thees forums cover a broad range of networking topics (before 01/01/2002). ). Dacă sistemul nu a pornit încă jobul QZLSSERVER, porniţi-l folosind domanda CL STRTCPSVR *NETSVR. You are then no longer dependant on whether QSERVER starts first, whether the autostart job entry is there or not, etc. CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER from ending has been removed. To determine the location where the user ID is disabled for NetServer use, you should look at the Cause section of the message. . . CWBSY1018 RC613. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). So your table should look something like that. Cause . Sorted by: 62. . 0 EVTW PTF Group Status DEV IBM PTF Group Level Description Level Available SF99711 8 ALL PTF GROUPS EXCEPT CUMULATIVE PTF PACKAGE 8 12-Jan-18 SF99710 17192 CUMULATIVE PTF PACKAGE IBM C7192719 17192 28-Jul-17 SF99709 223 GROUP HIPER 223 12-Jun-18 SF99708 83 GROUP SECURITY 83 29-May-18 SF99707 11 TECHNOLOGY REFRESH 11 19-Nov-15 To determine what job or user ended Netserver, press F1 on the CPC1125 message and then press F9 to get message details. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. The QZLSSERVER is automatically started every time the QSERVER subsystem is started. 3 - Exchange user profile failed. . 4. When I look at Netserver config in Ops Nav - no. You should be able to see a job QZLSSERVER in subsystem QSERVER if it is active. To start NetServer, type STRTCPSVR *NETSVR and then DSPMSG QSYSOPR to verify. This is because the NetServer code swaps to the QSECOFR profile before issuing the command to end the QZLSSERVER job. Because of this, no changes are needed in your startup program if the QSERVER subsystem is started before TCP/IP is. QZLSSERVER QPGMR BCH ACCOUNTING QSYS SBS QZLSFILE QUSER PJ QZLSFILET QUSER PJ SALES_NW QSYS SBS QZLSFILE QUSER PJ QZLSFILET QUSER PJ You decide where iSeries NetServer jobs will run. ÂSee the following reason codes and Âtheir meanings: Ensure that your IBM i hostname maps to it's IP adress and vice versa, in both DNS and WINS (if you're using WINS). : QPGMRQZLSSERVER is IBM Net Server. One has ended. Messages appear in the QSYSOPR message queue, stating that the QZLSSERVER or QZLSFILE jobs were ended by user QSECOFR even though no user has signed on as QSECOFR to end these jobs. . CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER from ending has been removed. 4 - Unable to obtain lock for service program QZLSSRV1 in. Let me expand upon this. CORRECTION FOR APAR 'SE77401' :-----A timing window exists where multiple IBM i NetServer jobs may attempt to clean up internal resources at the same time. will be corrected so that the hard coded value in the kerberos. Unable to retrieve host IP address because of return code 3. When I looked at the previos sign on date for this profile, it had not been used to sign on in over a month prior to this event happening the other day. The QZLSSERVER is automatically started every time the QSERVER subsystem is started. The QZLSFILE prestart jobs support single. . If the QZLSSERVER job is not active, you must restart iSeries NetServer. 5. iSeries NetServer is not properly cleaning up unprocessed client requests which causes iSeries NetServer to not end. . Please help! 'The required AS/400 NetServer job QZLSSERVER wa unable to start because of reason code 6. All from 11/07/03. I know that STRHOSTSVR *ALL starts this job but my question is can I invoke this specific job without having to end/start the QSERVER subsystem and, ifQZLSSERVER joblog will hit a repeated msgMCH6906 f/#hmfremi t/QKRBGSS and intermittentent msgC2M1212 f/QC2UTIL1 t/QZLSKERB1 and msgCPD3E3F f/t/QKRBSPI. 3 - Exchange user profile failed. See the following reason codes and their. There is also a job QZLSFILE that is the file share job which may shed some light if there is anything going on at the iSeries end of things. See the QZLSSERVER job under the QSERVER subsystem. 2 - Unable to retrieve credentials. What is Kerberos: Kerberos is an network authentication protocol that: Provides strong authentication for client/server applicationsUses secret-key cryptographyAllows mutual. Network authentication service Network authentication service allows the iSeries and several iSeries services, such as iSeries Access for Windows, to use a Kerberos ticket as an optional replacement for a user name and password forThe internal search function is temporarily non-functional. When I see our admin, I will ask him about the two jobs. ibm. Then select option 2, Work with Activation. Cause . The Start Server (QZSLSTRS) and End Server (QZLSENDS) APIs start and end the server. After that, message CPIB683 is sent to QSYSOPR with reason code 6 and return code 3204 (I think; sorry, I can't remember the exact figure. comp. My old computer, win2k, has no problems. Is the IBM i file path shared? Open IBM i Navigator and go to File Systems, File Shares. If Netserver was ended from System i Navigator, the details will show the remote command job (QZRCSRVS) servicing that request. . Network Security uses several exit programs that interact with the various servers on IBM i. Problem Conclusion. Press the Enter key. 2 - Unable to retrieve credentials. QSYS/QTOINETD. . If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. on the sure password list list × The internal search function is temporarily non-functional. These forums cover a broad range of programming topics (before 01/01/2002). . After that, message CPIB683 is sent to QSYSOPR with reason code 6 and return code 3204 (I think; sorry, I can't remember the exact figure. I assume it's trying to figure out what IP address to bind too or something. If these connections are not displayed, start NetServer again. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. Press the Enter key. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. For the servers to use the exit programs, the exit programs must be registered. Verify that the system has started the QZLSSERVER job within QSERVER. . The QZLSSERVER job is in the QSERVER subsystem. Sur un nouvel AS400 en V5. Shortly after the messages start occurring, Netserver becomes unusable. Re: NetServer -- If you hit F1 on one of those messages, and then hit F9 for message details, you will see the actual job which issued the command. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. IBM i NetServer jobs will, on rare occasion, take an extended period of time to end. To activate Powertech Exit Point Manager. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 10. then selecting networks, then selecting servers, then selecting TCP/IP. By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 5. You can specify whether or not the AS/400 NetServer starts automatically when TCP/IP is started by selecting the “Start when TCP/IP is started” check box on the. -----Original Message-----From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt Sent: Wednesday, July 06, 2016 10:03 AMThe history log QHST contains the past system-operator messages, device status, job-status changes, and program-temporary-fix activities that are stored as system messages. 2 - Unable to retrieve credentials. The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. NetServer mapped drive access becomes slower and slower until they reach a point where they are unusable. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. 11. . You are here: Getting Started > Activating Powertech Exit Point Manager Activating Powertech Exit Point Manager Exit Point Manager uses several exit programs that. DSPLOG QHST JOB(QZLSSERVER) Press the Enter key. Cause . Cause . The QZLSSERVER job and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete internal. period of time to end. 3. . iSeries NetServer is not properly cleaning up unprocessed client requests which causes iSeries NetServer to not end. . . . Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). Cause . Steps to get NetServer-related task dumps: 1) Execute: STRSST <enter>. QZLSSERVER QPGMR 185084 BATCH JOBLOG PENDING 01/05/11 QZLSSERVER QPGMR 184987 BATCH JOBLOG PENDING 01/05/11 Bottom F3=Exit F12=Cancel Duplicate jobs found. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. . Licensed Internal Code (LIC) data 14. *DIRSRV is LDAP. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. Verify that the system has started the QZLSSERVER job within QSERVER. Determining if NetServer is Running: Use the Work with Active Job command to verify there is a QZLSSERVER job running under the QSERVER subsystem. . . When Netserver starts, it sends out a DNS query for it's assigned name. Internet Daemon (INETD) SuperServer. Typically, the start of sbs QSERVER. Special Instructions None. 2 - Unable to retrieve credentials. Reason Code 6 = Start of the internal server failed with return code 3409. To Start: 1) Starts when the subsystem starts 2) If subsystem is active and the jobs are not active, issue STRPJ SBS(subsystem name) PGM(QSYS/QZLSFILE), where subsystem name is QSERVER. The current search engine is no longer viable and we are researching alternatives. The help for that message only adds some. Ověřte, zda již systém spustil úlohu QZLSSERVER v subsystému QSERVER. Take option 2 for LDAP Data Collection. Re: NetServer -- The Display Log (DSPLOG) [feature used to display the History Log (QHST)] offers a means to include worthwhile context [second-level text and job issuing the message], rather than showing solely those first-level message text, using a form of spooled output [similar to how the spooled joblog can include significantly more context than just. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). If the QZLSSERVER job is not active, you must restart IBM i NetServer. . you can check it out there. . From program: QKRBGSSFrom library: QSYSFrom module: KRB_DNSFrom procedure: get_kdc_listTo program: QKRBGSSTo library: QSYSTo module: KRB_DNSTo procedure: get_kdc_list. The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. . 2 - Contact your service provider. . If I were to end the other, how would it get restarted? John McKee On Mon, Sep 10, 2012 at 2:34 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:IBM eServer iSeries © 2003 IBM Corporation Session Objectives Awareness of NetServer enhancements in V5R1 and V5R2. You can specify whether or not the AS/400 NetServer starts automatically when TCP/IP is started by selecting the “Start when TCP/IP is started” check box on the AS/400 NetServer General. Skip to main content. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. . If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. . : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. . The current search engine is no longer viable and we are researching alternatives. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . The IBM i NetServer QZLSSERVER job experiences high paging levels when SMB2 is in use. We are having issues receiving large files over SSL FTP connections on our iSeres (AS/400) FTP server, but when we send the same file through standard FTP (non-SSL) it works fine. From an OS/400 command line, enter CFGTCP and select Option 10. . Ellenőrizze, hogy a QZLSFILE előindított job vár-e programindítási kérésre (PSRW állapot a Work with Active Jobs> képernyőn). To determine the available log versions, use the Display Object Description (DSPOBJD) command. Verify that the system has started the QZLSSERVER job within QSERVER. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. The QZLSFILET or QZLSFILE job might be in the QSERVER subsystem for each active client user that connects to an IBM i NetServer file share. See the following reason codes and their meanings: . . 23 is invalid. MIMIX HA Runbook Template Availability Runbook Vision: iSeries Availability Runbook Template Overview For the most current version of this template look on the Vision web…IBM eServer iSeries © 2003 IBM Corporation Session Objectives Awareness of NetServer enhancements in V5R1 and V5R2. If root cause is to be determined, the following diagnostic materials must be gathered before any recovery action is taken. Network Security uses several exit programs that interact with the various servers on IBM i. QZLSSERVER QPGMR BCH ACCOUNTING QSYS SBS QZLSFILE QUSER PJ QZLSFILET QUSER PJ SALES_NW QSYS SBS QZLSFILE QUSER PJ QZLSFILET QUSER PJ You decide where iSeries NetServer jobs will run. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. As an Amazon Associate we earn from qualifying purchases. If the job is not used during the previous two hours, it is ended. . To Start: 1) Starts when the subsystem starts 2) If subsystem is active and the jobs are not active, issue STRPJ SBS(subsystem name) PGM(QSYS/QZLSFILE), where subsystem name is QSERVER. Problems are logged with symptom string QZLSSERVER MCH6903 - 5770 sp/qgldheap. . Run the following operating system. The internal search function is temporarily non-functional. Solution 2: Make sure the EIM domain controller password matches the LDAP administrator password. Write down the. . Activating Powertech Network Security. Some servers are started by using CL commands, such as STRTCPSVR *DHCP. or DDM Connection fails with message CPD3E3F when connecting to target IBM i:CPD3E3F. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 13. CWBSY1018 RC613. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. Tom - I have a 170 running V5R1M0 with 5722999 (Licensed Internal Code) cum TL02134 and 5722SS1(OS/400) cum TC02134. > QZLSSERVER > 2. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. In your start program start the subsystem QSERVER > 5. Ha a beállítás értéke *YES, akkor a szerver a TCP/IP indításakor automatikusan elindul. Cause . So if someone maps a drive to /youribmi/yourshare it should appear in these. If you have to ask what LDAP is, then you do not need to start *DIRSRV at this time. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. Check the QZLSSERVER joblog using the following CL command: WRKACTJOB JOB(QZLSSERVER) 2. However, the QZLSSERVER job did not end, which caused iSeries NetServer not to start. . ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. If the QZLSSERVER job is not active, you must restart IBM i NetServer. . . Typically, the start of sbs QSERVER happens before STRTCP). Enter the command to start iSeries Netserver. An IPL of the system is needed to allow iSeries NetServer to start and clients to connect. Check the QZLSSERVER joblog using the following CL command: WRKACTJOB JOB(QZLSSERVER) 2. John McKee On Mon, Sep 10, 2012 at 1:44 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:Cause . Pentru pornire:Verify that the system has started the QZLSSERVER job within QSERVER. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. 5 - Start iSeries NetServer with the reset option using. mf45396 8365 01/12/09 lic-wait netserver job qzlsserver will not mf56824 end mf45403 8365 11/12/08 lic-comm-srcb6005121-incorrout termination with active hea mf45410 8288 09/16/08 lic-perfm task quantum expiration mf56613 mf45434 8365 09/11/08 wait-hlic-9406misc iasp vary off hung when. Alternatively, from the. . So if someone maps a drive to /youribmi/yourshare it should appear in these. Enter a 1. : Â The required iSeries NetServer job QZLSSERVER was unable Âto start because of reason code 13. The internal search function is temporarily non-functional. CORRECTION FOR APAR 'SE77401' :-----A timing window exists where multiple IBM i NetServer jobs may attempt to clean up internal resources at the same time. '0' - Reset (0 indicated no. 3. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. A dump of internal NetServer task activity is useful when QZLSFILET or QZLSSERVER does not end. When a comparison is made. See the following reason codes and their meanings: 1 - Unable to retrieve user. No newVerify that the system has started the QZLSSERVER job within QSERVER. The major issue was that the upgrade recycled QSERVER and ended some jobs from QUSRWRK. Other servers start when certain subsystems. Check for QZLSSERVER joblogs for errors (WRKSPLF QPGMR). If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. This. Verify that the system has started the QZLSSERVER job within QSERVER. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. . 13 - The retrieved host IP address of 209. The cause of the problem is a memory leak in the EIM/LDAP code. The IBM i NetClient file system (QNTC) relies on NetBIOS services to auto-populate the QNTC path with servers. Cause . From the History (DSPLOG): Job 265084/QPGMR/QZLSSERVER started on 08/26/09 at 10:57:03 in subsystem QSER. 0 PS QZLSSERVER QPGMR 776279 0 0 QLESPI QSECOFR 0 0 0 03/16/15 18:06:58 0 Jim Franz--This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To. 6/1/06 By: Tom Huntington Understanding The IFS The Basics File Systems Commands Journaling Save/Restore Security The Basics Added to OS/400 V3R1 in 1994 Integrates iSeries with UNIX, Windows, and others Directory structure much like your PC Provides access to data stored in integrated or remote xSeries servers, Novell servers,. Verify that the system has started the QZLSSERVER job within QSERVER. . Problem Conclusion. There will no longer be a QZLSSERVER autostart job in the QSERVER subsystem description, but the QZLSSERVER job will still reside in the QSERVER subsystem. CORRECTION. There are multiple QZLSFILE jobs in a subsystem, and each one supports one client and all of the thread unsafe file shares that are accessed by a Windows client when using IBM i. 2 - Unable to retrieve credentials. The NetServer QZLSSERVER job uses increasing amounts of CPU overIBM i NetServer. To prompt the command, select F4. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . Ellenőrizze, hogy a QZLSFILE előindított job vár-e programindítási kérésre (PSRW állapot a Work with Active Jobs> képernyőn). 0. . ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. The QPGMR job QZLSSERVER is the program used to end that job, which had to be initiated by another job/user, which all indicate it was QSECOFR. 0 to 8. I have. The current search engine is no longer viable and we are researching alternatives. Network Print also requires that the Loopback. . The QZLSSERVER job is in the QSERVER subsystem. Je n'accède plus à l'IFS et QDLS, je ne voit que DIRSRV et QIBM. The security auditing function must be set up before you can use this command. Activating Powertech Exit Point Manager. '. To prompt the command,. If QZLSSERVER is not active, then NetServer is not started. If the QZLSSERVER job is not active, you must restart IBM i NetServer. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. 22,PowertechExitPointManagerwasnamedPowertechNetwork. Dump to printer 2. . Problem Summary. CPF0920 All prestart jobs for program QZLSFILE in library QSYS in subsystem QSERVER are ending for reason 1. To display these options, from the Exit Point Manager Main Menu, select option 81, Configuration Menu. and sign on to SST If there is no SRC displayed under front panel Function 11, and the Service Action Log is clear, press ENTER on the Selection screen, then press F6 "Acknowledge All Errors" to turn off the System Attention light, then press F10 when prompted to confirm. . Inside the IFS. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. NetServer sends a warning message to the QSYSOPR message queue to indicate that NetBIOS services are not available, but the QZLSSERVER server job starts and accepts connections on port 445. Using the Work with TCP/IP Network Status (NETSTAT *CNN) command, the following entries are shown. ). Activating Powertech Network Security. Frequent Query Directory operations will cause a lot of system activityqzlsserver qpgmr 186513 batch joblog pending 01/08/11 qzlsserver qpgmr 186120 batch joblog pending 01/07/11. CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER from ending has been removed. a hang preventing QZLSSERVER from ending. . 3 - Exchange user profile failed. . Activation Instructions None. Select a “Job name” of QZLSSERVER (iSeries Netserver’s job name on the iSeries). Write down the name from the Server name field. For this purpose, I created 1 same user account on the network and on the AS/400 and set the right authorities. For the servers to use the exit programs, the exit programs must be registered. As an Amazon Associate we earn from qualifying purchases. If the QZLSSERVER job is not active, you must restart IBM i NetServer. . WRKACTJOB SBS(QSERVER) JOB(QZLSSERVER) If the QZLSSERVER job is not active, then NetServer is not active and must be started, using one of the options above. The internal search function is temporarily non-functional. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). qzlsserver qpgmr bch pre v5r2 v5r2 opt subsystem/job user type qserver qsys sbs qpwfservsd quser bch qserver qpgmr asj qzdasrvsd quser bch qzlsserver qpgmr bch accounting qsys sbs qzlsfile quser pj qzlsfile quser pj QZLSSERVER QPGMR BCH . This may help us to determine if it was a regular workstation interactive job, or some utility job such as and. Ok, maybe return to the "two server jobs"?? If both are still running: (one, if I recall, in "create joblog" status ?) Kill one, kill both, end/restart subsystem ?Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. 2 - Unable to retrieve credentials. In System i Navigator go to Netowkr --> Enterprise Identity Mapping and right click on 'Configuration' and click on 'Properties'. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. . 3 - Exchange user profile failed. Conversations. This CPU increase is associated with heavy use of the NetServer network printing function. . My admin says you should end and then re-start the subsystem, and that is what I >think< also, but another check of the IBM site might be worth your time, as well as making a list ofThese forums cover a broad range of programming topics (before 01/01/2002). The internal search function is temporarily non-functional. Other jobs are also restarted, like. See the QZLSSERVER job under the QSERVER subsystem. The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. This. Activating Powertech Network Security. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. Java time stamps are used for this comparison, so it is. WRKACTJOB JOB(QZLSSERVER) If a job is displayed, the server is active.