4. 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. John McKee On Mon, Sep 10, 2012 at 10:17 AM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote: John, Our system i admin said he would check possible conflict due toThe IBM i NetServer QZLSSERVER job experiences high paging levels when SMB2 is in use. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). The QZLSSERVER job is in the QSERVER subsystem. If the QZLSSERVER job is not active, you must restart IBM i NetServer. : QPGMRa hang preventing QZLSSERVER from ending. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). WRKACTJOB JOB(QZLSSERVER) If a job is displayed, the server is active. 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. 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). 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. then selecting networks, then selecting servers, then selecting TCP/IP. All of the above means that Halcyon will check your iSeries system at 07:00, raise an alert if it cannot find iSeries Netserver running in the QSERVER subsystem, then run the command to start the job. (See "Silent Vigil: Logging Security Violations," MC, October 1992 and "Powerful Audit Functions Enhance V2R3. 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. . Client Access network printing daemons be gone! ARCHIVE. (I don't have access to it on our systems, so I can't be more specific. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. 2 - Unable to retrieve credentials. 2 - Unable to retrieve credentials. CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. 4. Our Curbstone. 3 - Exchange user profile failed. The usual way to store password, is to use a hash function on the password, but to salt it beforehand. Használja a Work with TCP/IP Network Status (NETSTAT *CNN) parancsot annak ellenőrzéséhez, hogy a következő. Resolving The Problem. Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the To stop and start AS/400 NetServer, use the following commands: STRTCPSVR *NETSVR ENDTCPSVR *NETSVR I have made All configuration changes made to AS/400 NetServer, - WRKACTJOB) command to verify that there is a. IBM Tivoli Directory Server: LDAP: WRKACTJOB JOB(QUSRDIR) If a job is displayed, the server is active. . . CIRCUMVENTION FOR APAR MA47776 :-----None. See the following reason codes and their meanings: . The QZLSSERVER job and QZLSFILE jobs mayQZLSSERVER QPGMR 185469 BATCH JOBLOG PENDING 01/06/11 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. How to Get There. The current search engine is no longer viable and we are researching alternatives. So you've got a DNS or host table entry for the Netserver name with the old IP address. The internal search function is temporarily non-functional. . 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. 6. . : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 5. Before I started the QZLSSERVER job, there were several active QPWFSERVSO jobs running. . . The internal search function is temporarily non-functional. Jestliže systém ještě nespustil úlohu QZLSSERVER, spusťte ji CL příkazem STRTCPSVR *NETSVR. * * netbios > 001:27:44 ListenCause . The QZLSSERVER job and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete internal processing. NetServer mapped drive access becomes slower and slower until mapped drive access reaches a point where it is unusable. 7 is invalid. . Verify that the system has started the QZLSSERVER job within QSERVER. Provjerite da je sistem pokrenuo QZLSSERVER posao unutar QSERVER. In your start up program (or as an autostart job entry in QSYSWRK) start > TCP/IP > 4. CIRCUMVENTION FOR APAR MA47776 :-----None. ). Ha a QZLSSERVER feladat nem aktív, akkor indítsa újra az i5/OS NetServert. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. . . ). . This is because the NetServer code swaps to the QSECOFR profile before issuing the command to end the QZLSSERVER job. No newVerify that the system has started the QZLSSERVER job within QSERVER. 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. "Thees forums cover a broad range of networking topics (before 01/01/2002). This may help us to determine if it was a regular workstation interactive job, or some utility job such as and. How do you know the passwords are the same - what happens if you enter thewrkactjobコマンドでqserverサブシステム配下に qzlsserverジョブが実行中であることを確認 さらにNETSAT *CNNコマンドを使用して以下の行の存在を確認することでNetServerが正常に起動していることを確認できます。fyi: We identified the profile swap as an event when Netserver restarts (we restart tcp after save active locks achieved) for any profile that wasActivating Powertech Network Security. Problem Summary. Activating Powertech Network Security. IBM i NetServer jobs will, on rare occasion, take an extended period of time to end. On Mon, Sep 10, 2012 at 12:51 PM, John McKee <jmmckee@xxxxxxxxxxxxxx> wrote: Profile is not disabled. · The NETSERVER job is startedCheck for a job named QZLSSERVER. The help for that message only adds some. Network Security uses several exit programs that interact with the various servers on IBM i. So your table should look something like that. I have v4r5 and check to see if its active by opening operations navigator and selecting the system I want. Apparently, there is a problem when the system tries to start NetServer which causes the system to lock-up. . You can track this item individually or track all items by product. . 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,. No caps or special characters in password. 4 - Use the Work with Object Locks (WRKOBJLCK) command to find the owner of the lock and take steps to remove the lock. Reboot of XP didn't fix it. . 4 - Unable to obtain lock for service program QZLSSRV1 in. . However, QZLSFILET and QZLSFILE jobs can run in another subsystem if the user has configured other subsystems to run IBM i NetServer jobs. 8. Problems are logged with symptom string QZLSSERVER MCH6903 - 5770 sp/qgldheap mod/qgldheap. 3 - Exchange user profile failed. . See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. 3. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). Verify that the system has started the QZLSSERVER job within QSERVER. 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. . . The Autostart servers parameter appears at the top of the list of parameters. For the servers to use the exit programs, the exit programs must be registered. . 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. 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 . 11/11/2003. : QPGMRQZLSSERVER is IBM Net Server. Cause . : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 5. Sur un nouvel AS400 en V5. . AboutIf the QZLSSERVER job is not active, you must start IBM i NetServer. Check for QZLSSERVER joblogs for errors (WRKSPLF QPGMR). ). 注: マネージメント・セントラルには、QSYSOPR からのメッセージをモニターする機能があります。 管理者はこの機能を使用して、 IBM i NetServer で使用不可になっているプロファイルについてアラートを受けることができます。 管理者は System i® ナビゲーター を使用して、 使用不可になった. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. Sent: Wednesday, August 26, 2009 12:21 PM To: Midrange Systems Technical Discussion Subject: RE: NetServer Not Starting The QZLSSERVER job is. One has ended. 23 is invalid. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 5. This is how to start Netserver from an IPL: Remove the autostart job entry from the QSERVER subsystem for job QZLSSERVER with RMVAJE SBSD (QSYS/QSERVER) JOB (QZLSSERVER) (This prevents the autostart job from trying to start Netserver before TCP/IP is up. . code is changed to the job CCSID before a comparison is made. <Murphey2, I will likely do as you have done with the same user accounts, however my issue still remains. CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER from ending has been removed. John McKee On Mon, Sep 10, 2012 at 11:48 AM, Jack KingsleyThe internal search function is temporarily non-functional. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. Skip to navigationI think the QZLSFILE job comes up once there is a share; the QZLSSERVER (?) job may have a job log that indicates if there is an authentication issue. See reason 1 shown below: 1 - The End Prestart Job. 2 - Unable to retrieve credentials. 3 - Exchange user profile failed. QZLSSERVER is the NetServer job. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. The help for that message only adds some. QZRCSRVS cleanup. Bonjour à tous, J'ai un AS400 en v5. : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 13. The current search engine is no longer viable and we are researching alternatives. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. The current search engine is no longer viable and we are researching alternatives. Default Instructions Verify that the system has started the QZLSSERVER job within QSERVER. Shortly after the messages start occurring, Netserver becomes unusable. 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. If the jobs are already running, the API will fail. Activation Instructions None. comp. )The internal search function is temporarily non-functional. QZLSSERVER Joblog 1. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. . ----- FlyByNight Software OS/400, i5/OS Technical Spec Cause . In fact, when 1st started, computer on, but user not in the building. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. . . : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. You can track this item individually or track all items by product. a hang preventing QZLSSERVER from ending. CWBSY1018 RC613. . When Netserver starts, it sends out a DNS query for it's assigned name. It determines if the job was used at least twice within the maximum job monitor interval length. Network Print also requires that the Loopback. Determining if NetServer is Running: Use the Work with Active Job command to verify there is a QZLSSERVER job running under the QSERVER subsystem. Does anyone know what this means? Scott Coffey 2005-11-01 20:08:03 UTC. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. Cause . A dump of internal NetServer task activity is useful when QZLSFILET or QZLSSERVER does not end. As an. See reason 1 shown below:QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. . From the Exit Point Manager Main Menu, select option 81, Configuration Menu. Because the prestart job entry was removed from the subsystem, the QZLSFILET job will not start when NetServer is restarted. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. Write down the Host name and Domain name fields. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. 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. Points. CPF0920 All prestart jobs for program QZLSFILE in library QSYS in subsystem QSERVER are ending for reason 1. . QSYSWRK. 開始方法: 1) サブシステムの開始時に開始 2) サブシステムがアクティブであり、なおかつジョブがアクティブではない場合に、STRPJ SBS(subsystem name) PGM(QSYS. The file is about 250 meg. These forums cover a broad range of programming topics (before 01/01/2002). 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). Eg: QMGR A has several QMGRS(B,C,D,E,F. Problem Summary. a hardcoded value which is in CSID 37. To display these options, from the Network Security Main Menu, select option 81, Configuration Menu. In a cluster environment , I see channels to a particular server is ending abnormally and resuming frequently in a day. Work with Exit Point Manager Activation. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. . The current search engine is no longer viable and we are researching alternatives. The internal search function is temporarily non-functional. IBM i NetServer Connections - Using the Work with TCP/IP Network Status (NETSTAT *CNN) command you should see the following entries. The Start Server (QZLSSTRS) API starts the jobs necessary for the IBM ® i Support for Windows ® Network Neighborhood (IBM i NetServer™) server to run. . Post-Switch Tasks These tasks should be performed immediately after to the switch: Step Action Time done 10 On the , check that: The TCP/IP interface is active use command NETSTAT for this The TCP host name is set to use command CFGTCP option 12 for this The NETSERVER job is started Check for a job named QZLSSERVER 11 Record all. Thees forums cover a broad range of networking topics (before 01/01/2002). . This is how to start Netserver from an IPL: Remove the autostart job entry from the QSERVER subsystem for job QZLSSERVER with RMVAJE SBSD (QSYS/QSERVER) JOB (QZLSSERVER) (This prevents the autostart job from trying to start Netserver before TCP/IP is up. Verify that the system has started the QZLSSERVER job within QSERVER. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). The cause of the problem is a memory leak in the EIM/LDAP code. Verify that the system has started the QZLSSERVER job within QSERVER. The current search engine is no longer viable and we are researching alternatives. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. 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. 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. See also Manual Restart After Activation. If the QZLSSERVER job is not active, you must restart i5/OS NetServer. . Indítás: 1) Elindul az alrendszer indításakor 2) Ha az alrendszer aktív és a jobok nem aktívak, akkor adja ki a STRPJ SBS(alrendszer neve) PGM(QSYS/QZLSFILE) parancsot, ahol az alrendszer neve. When I look at Netserver config in Ops Nav - no. Select “Action type” of COMMAND. Reason Code 6 = Start of the internal server failed with return code 3409. RE: NetServer Not Starting -- Find the NetServer host job (QZLSSERVER) and see if it shows anything helpful. No newJudging by the fact that it should have started I should probably put an automatic check in there to assure that it does with the additional CALL. Some servers are started by using CL commands, such as STRTCPSVR *DHCP. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. . As an Amazon Associate we earn from qualifying purchases. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. © Copyright International Business Machines Corporation 1998, 2002. Problem Conclusion. Default InstructionsCause . . 4 - Unable to obtain lock for service program QZLSSRV1 in. So the next step is to check out. LIC-OTHER INTERNAL EXTENSIONS FOR MAINTAINABILITY [{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. code is changed to the job CCSID before a comparison is made. If the QZLSSERVER job is not active, you must restart IBM i NetServer. Authors; Categories; Articles; BOOKSTORE . . Solution 1: Make sure that the LDAP server (typically QUSRDIR job) is active. . . Ako sistem nije već pokrenuo QZLSSERVER posao, pokrenite ga koristeći CL naredbu STRTCPSVR *NETSVR. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). Determining if NetServer is running: Use the Work with Active Job (WRKACTJOB) command to verify there is a QZLSSERVER job running under the QSERVER subsystem. 4 - Unable to obtain lock for service program QZLSSRV1 in. From what I can gather when I connect to the FTP Server with out. Check the QZLSSERVER joblog using the following CL command: WRKACTJOB JOB(QZLSSERVER) 2. In IBM i Navigator, navigate under the system in question to Network -> Servers -> TCP/IP, right click on IBM i NetServer, and select Properties. The current search engine is no longer viable and we are researching alternatives. 215. Problem Summary. 7. Cause . : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. period of time to end. Verify that the system has started the QZLSSERVER job within QSERVER. The IBM i NetServer QZLSSERVER job experiences high paging levels when SMB2 is in use. Shortly after the messages start occurring, Netserver becomes unusable. Job neve: A szerver aktív jobjának vagy jobjainak neve. 3 - Exchange user profile failed. . Please help! 'The required AS/400 NetServer job QZLSSERVER wa unable to start because of reason code 6. a hardcoded value which is in CSID 37. This address not in our network, & not on our iSeries. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . . See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. Look for the QZLSSERVER job. 2 - Unable to retrieve credentials. The NetServer QZLSSERVER job starts using CPU over a period of time and the CPU keeps increasing each day until an IPL. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 10. Then select option 2, Work with Activation. Number . The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. . 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. 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. Cause . The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. you can check it out there. See the following reason codes and their meanings: 1 - Unable to retrieve user. Ouch. If root cause is to be determined, the following diagnostic materials must be gathered before any recovery action is taken. To view or change the Autostart servers parameter, follow these steps: . QZLSSERVER joblog will hit a repeated msgMCH6906 f/#hmfremi t/QKRBGSS and intermittentent msgC2M1212 f/QC2UTIL1 t/QZLSKERB1 and msgCPD3E3F f/t/QKRBSPI. OversightReview 46 GranulatingRulesforSpecificNeeds 49 OngoingAuditing 50 IntegrationswithOtherFortraProducts 50 KeepingPowertechExitPointManagerforIBMiUp-to-Date 50Activating Powertech Network Security. Cause . . The current search engine is no longer viable and we are researching alternatives. If the QZLSSERVER job is not active, you must restart IBM i NetServer. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. For example, CHGFTPA to work with the attributes of the FTP server. 11. *DIRSRV is LDAP. Las API de Arrancar servidor (QZSLSTRS) y Finalizar servidor (QZLSENDS) aún arrancan y finalizan el servidor. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. 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. Enter the appropriate values. server is running with CCSID 277 and the kerberos code is using. From the History (DSPLOG): Job 265084/QPGMR/QZLSSERVER started on 08/26/09 at 10:57:03 in subsystem QSER. The current search engine is no longer viable and we are researching alternatives. To determine the location where the user ID is disabled for NetServer use, you should look at the Cause section of the message. Ověřte, zda již systém spustil úlohu QZLSSERVER v subsystému QSERVER. So if someone maps a drive to /youribmi/yourshare it should appear in these. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. Our Network and AS/400 User-ID's are not the same, so I had the same problem. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). 2 - Unable to retrieve credentials. I will try a reboot. The internal search function is temporarily non-functional. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . WelcometoPowertechExitPointManagerforIBMi/ WelcometoPowertechExitPoint ManagerforIBMi WARNING:Priortoversion7. However, the QZLSSERVER job did not end, which caused iSeries NetServer not to start. QSYS/QZLSSERVER: QSERVER: QZLSSERVER * 예: 137 TCP(netbios-ns) 137 UDP(netbios-ns) 138 UDP(netbios-dgm) 139 TCP(netbios-ssn) 445 TCP(cifs) IBM i NetServer. QZLSSERVER job running 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. 3. 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. Network Security uses several exit programs that interact with the various servers on IBM i. If no active QZLSSERVER job is found, then NetServer is not started. . . CORRECTION. If the QZLSSERVER job is not active, you must restart IBM i NetServer. Because of this, no changes are needed in your startup program if the QSERVER subsystem is started before TCP/IP is. The QZLSSERVER is automatically started every time the QSERVER subsystem is started. This. 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. Gary, but user is not actively doing anything. Activating Powertech Network Security. In System i Navigator go to Netowkr --> Enterprise Identity Mapping and right click on 'Configuration' and click on 'Properties'. Sorted by: 62. Inside the IFS. Looking at theQSYSOPR msgq, and the QHST log, I found jobs related to the Netserver that were ended by QSECOFR. 1. . See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. The msgMCH6906 messages occur up to 10 times per second and cause the joblog to wrap. ). : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. Alternatively, from the operating system command line, type the following: WRKJOB QZLSSERVER Press the Enter key. The following describes the parameters and allowable values for each field on the Work with Activation panel.