For a list of common NetServer startup errors and possible causes, review the chart below. code is changed to the job CCSID before a comparison is made. Look for the QZLSSERVER job. 2 - Unable to retrieve credentials. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). În majoritatea cazurilor, acesta este numele serverului aşa cum apare în System i Navigator. 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. See the QZLSSERVER job under the QSERVER subsystem. From an OS/400 command line, enter CFGTCP and select Option 10. iSeries NetServer is not properly cleaning up unprocessed client requests which causes iSeries NetServer to not end. . When a comparison is made. ). The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. . Verificaţi dacă job prestart QZLSFILE aşteaptă o cerere de pornire a programului (starea PSRW despre lucrul cu afişarea joburilor active. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. . 3 - Exchange user profile failed. If the QZLSSERVER job is not active, you must restart IBM i NetServer. . Using the Work with TCP/IP Network Status (NETSTAT *CNN) command, the following entries are shown. . The internal search function is temporarily non-functional. Cause . However, I have a drive mapped and I only have one QZLSSERVER job and it's "current user" is QPGMR Current user profile . If no active QZLSSERVER job is found, then NetServer is not started. I will try a reboot. If "Include LIB" is set to Y, it includes the QUSRDIRDB, QUSRDIRCF, and QUSRDIRCL library saves. 3 - Exchange user profile failed. 2 - Unable to retrieve credentials. Cause . ----- FlyByNight Software OS/400, i5/OS Technical Spec Cause . Steps to get NetServer-related task dumps: 1) Execute: STRSST <enter>. Problem Summary. Table of Contents © 2014 Tango/04 Computing Group Page iii Table of Contents Table of Contents. 1. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . 13 - Correct the name configured for IBM i NetServer which. . 3. Halcyon will continue to check for an active Netserver job but. 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. . . The current search engine is no longer viable and we are researching alternatives. 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. In System i Navigator go to Netowkr --> Enterprise Identity Mapping and right click on 'Configuration' and click on 'Properties'. See the following reason codes and their meanings: . Enter the appropriate values. On Mon, Sep 10, 2012 at 11:17 AM, Gary Thompson <gthompson@xxxxxxxxxxx>wrote:The internal search function is temporarily non-functional. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. CIRCUMVENTION FOR APAR MA47776 :-----None. : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 5. Start a service tool 4. For example, the following DSPOBJD. The current search engine is no longer viable and we are researching alternatives. The current search engine is no longer viable and we are researching alternatives. 4 Answers. Specify a “Subsystem” of QSERVER to avoid Halcyon spending unnecessary time looking for the job in any other subsystems. See the following reason codes and their meanings: 13 - The retrieved host IP address of 6. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. It is important to "salt" the password, to defend oneself against rainbow table attacks. . : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 5. However, the QZLSSERVER job did not end, which caused iSeries NetServer not to start. CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER. So your table should look something like that. Way too slow today. 3. The QZLSSERVER is automatically started every time the QSERVER subsystem is started. The QZLSSERVER job is in the QSERVER subsystem. a hang preventing QZLSSERVER from ending. Problem Summary. The current search engine is no longer viable and we are researching alternatives. period of time to end. What is Kerberos: Kerberos is an network authentication protocol that: Provides strong authentication for client/server applicationsUses secret-key cryptographyAllows mutual. you can check it out there. As an. Network Security uses several exit programs that interact with the various servers on IBM i. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. . 3 - Exchange user profile failed. . The NetServer QZLSSERVER job starts using CPU over a period of time and the CPU keeps increasing each day until an IPL. Ouch. (See "Silent Vigil: Logging Security Violations," MC, October 1992 and "Powerful Audit Functions Enhance V2R3. . Change the database and file servers to not start with TCP/IP (This can > be done from Ops Navigator) > 3. The QZLSSERVER job and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete processing. NOTE: The Interactive method stops and starts QCMN and QSERVER. Those details have the number/user/job that ended Netserver. Log on to AS400 iSeries system. Activating Powertech Network Security. The Display Audit Log (DSPAUDLOG) command is used to display or print entries from the security auditing journal, QAUDJRN. 4. Activating Powertech Network Security. . Regards, Simon Coulter. 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. To determine the location where the user ID is disabled for NetServer use, you should look at the Cause section of the message. . Check the QZLSSERVER joblog using the following CL command: WRKACTJOB JOB(QZLSSERVER) 2. Ha a rendszer még nem indította el a QZLSSERVER feladatot, akkor indítsa azt el a STRTCPSVR *NETSVR CL parancs segítségével. Cause . . Reason Code 6 = Start of the internal server failed with return code 3409. AboutIf the QZLSSERVER job is not active, you must start IBM i NetServer. Activating Powertech Exit Point Manager. CALL QZLSSTRS PARM ('0' x'00000000') Start NetServer. Default InstructionsVerify that the system has started the QZLSSERVER job within QSERVER. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. Run the following operating system. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. Cause . Because of this, no changes are needed in your startup program if the QSERVER subsystem is started before TCP/IP is. Cause . : The required AS/400 NetServer job QZLSSERVER was unable to . 2 - Unable to retrieve credentials. 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 shared1. From iSeries Navigator: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. Activating Powertech Network Security. Thanks, but only one partition here. This address not in our network, & not on our iSeries. . . Recovery . 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. iiiBy 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 values do not match because of the CCSID difference. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. 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. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . . If the QZLSSERVER job is not active, you must restart IBM i NetServer. Our Network and AS/400 User-ID's are not the same, so I had the same problem. The NetServer QZLSSERVER job uses increasing amounts of CPU overIBM i NetServer. Special Instructions None. QZLSSERVER Joblog 1. This is how to start Netserver from an IPL: Remove the autostart job entry from the QSERVER subsystem for job QZLSSERVER with RMVAJE SBSD. . . Because the prestart job entry was removed from the subsystem, the QZLSFILET job will not start when NetServer is restarted. . Problem Summary. If the QZLSSERVER job is not active, you must restart i5/OS NetServer. then selecting networks, then selecting servers, then selecting TCP/IP. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . Shortly after the messages start occurring, Netserver becomes unusable. NetServer -- We had our Netserver end out of the blue the other day. . meanwhile, maybe check your subsystem jobs (detail of the "Start of prestart. There is a subsystem job called QZLSSERVER which, I think, serves requests from windows95 when browsing the IFS through explorer. 2 - Unable to retrieve credentials. Network Security uses several exit programs that interact with the various servers on IBM i. 2 - Unable to retrieve credentials. This. Outlook won't start. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. Dacă sistemul nu a pornit încă jobul QZLSSERVER, porniţi-l folosind domanda CL STRTCPSVR *NETSVR. ----- FlyByNight Software OS/400, i5/OS Technical Spec Cause . : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. QHTTPSVR. Shortly after the messages start occurring, Netserver becomes unusable. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). Subject: RE: Please check your communications path to the AS/400; From: "Gary Kuznitz " <docfxit@xxxxxxxxxxx>; Date: Mon, 18 Dec 2000 09:23:17 -0800Work with Activation. John McKee On Mon, Sep 10, 2012 at 1:44 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:Cause . A dump of internal NetServer task activity is useful when QZLSFILET or QZLSSERVER does not end. Cause . 3 - Exchange user profile failed. Because of this, no changes are needed in your startup program if the QSERVER subsystem is started before TCP/IP is. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . ibm. have you put on any latest patches on your computer. Las API de Arrancar servidor (QZSLSTRS) y Finalizar servidor (QZLSENDS) aún arrancan y finalizan el servidor. Verificaţi dacă sistemul a pornit jobul QZLSSERVER în cadrul QSERVER. Problem Conclusion. . . For the servers to use the exit programs, the exit programs must be registered. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. . 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. 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. NetServer mapped drive access becomes slower and slower until they reach a point where they are unusable. -----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. See the QZLSSERVER job under the QSERVER subsystem. 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. 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. 3 - Exchange user profile failed. For a list of common NetServer startup errors and possible causes, review the chart below. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. QZLSSERVER Joblog 1. Cause . ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. . In your start up program (or as an autostart job entry in QSYSWRK) start > TCP/IP > 4. 8. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. Ověřte, zda již systém spustil úlohu QZLSSERVER v subsystému QSERVER. Select Option 10 for the joblog. . HTTP Server-instance. : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 13. If root cause is to be determined, the following diagnostic materials must be gathered before any recovery action is taken. . So the next step is to check out. QZLSSERVER QPGMR 185494 BATCH JOBLOG PENDING 01/06/11 QZLSSERVER 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. . If the QZLSSERVER job is not active, AS/400 NetServer must be started. 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 QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 12. LIC-OTHER INTERNAL EXTENSIONS FOR MAINTAINABILITY [{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM. 23 is invalid. The current search engine is no longer viable and we are researching alternatives. To determine the available log versions, use the Display Object Description (DSPOBJD) command. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. A cleanup thread runs once an hour to determine whether a QZRCSRVS job is still being used by a Job Monitor. The Start Server (QZLSSTRS) API starts the jobs necessary for the IBM ® i Support for Windows ® Network Neighborhood (IBM i NetServer™) server to run. iSeries NetServer is not properly cleaning up unprocessed client requests which causes iSeries NetServer to not end. For the servers to use the exit programs, the exit programs must be registered. 2 - Unable to retrieve credentials. Solution 1: Make sure that the LDAP server (typically QUSRDIR job) is active. John McKee On Mon, Sep 10, 2012 at 11:48 AM, Jack KingsleyThe internal search function is temporarily non-functional. . The following describes the parameters and allowable values for each field on the Work with Activation panel. 3 - Exchange user profile failed. To display these options, from the Network Security Main Menu, select option 81, Configuration Menu. The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. IBM provides the Display Log (DSPLOG) CL command and the Open List of History Log Messages (QMHOLHST) API. Starting AS/400 NetServer starts QZLSSERVER and the four (4) Netbios connections can be seen in NETSTAT *CNN, but this lasts just 30 seconds. . Cause . Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. System ASP usage increases and eventually NetServer crashes with kerberos usage. Write down the Host name and Domain name fields. 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. 0 to 8. The QZLSSERVER is automatically started every time the QSERVER subsystem is started. I'm still not sure why that is, but my theory is that when they initially mapped the drive, the QZLSSERVER job spawns a QPWFSERVSO job which actually provides the drive mapping for a particular user. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. It brings up the servers. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). 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. Because several versions of each log might be available, you must select the log version to be processed. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. 11. Some servers are started by using CL commands, such as STRTCPSVR *DHCP. . If Netserver was ended from System i Navigator, the details will show the remote command job (QZRCSRVS) servicing that request. Verify the QZLSSERVER job is active using WRKACTJOB JOB(QZLSSERVER) at the 5250 Emulation screen prompt. Ověřte, zda předspuštěná úloha QZLSFILE čeká na požadavek na spuštění programu (stav PSRW na obrazovce Práce s aktivními úlohami). Before I started the QZLSSERVER job, there were several active QPWFSERVSO jobs running. . . QSYS/QTOINETD. I have. Verify that the system has started the QZLSSERVER job within QSERVER. Alternatively, from the operating system command line, type the following: WRKJOB QZLSSERVER Press the Enter key. will be corrected so that the hard coded value in the kerberos. 3 - Exchange user profile failed. The QZLSSERVER job and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete processing. We've been looking for the proper PTF to correct the. The QZLSSERVER job and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete internal processing. QZRCSRVS cleanup. Reconnect automatically Rebooted last Tuesday. Activation Instructions None. If root cause is to be determined, the following diagnostic materials must be gathered before any recovery action is taken. The current search engine is no longer viable and we are researching alternatives. 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. 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. Dump to printer 2. Recovery . This process has been running reliably for Note: While the Kerberos PTFs do not require a delayed apply / delayed remove, a pre-requisite necessary for QNTC does require an IPL to activate, although is built as an immediate apply / immediate remove as detailed in the activation instructions of the cover letter. . . 2 - Unable to retrieve credentials. sys. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). In properties, click on the General tab. For the servers to use the exit programs, the exit programs must be registered. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. To prompt the command, select F4. 13 - The retrieved host IP address of 209. You are here: Getting Started > Activating Powertech Exit Point Manager Activating Powertech Exit Point Manager Exit Point Manager uses several exit programs that. . When a comparison is made. Apparently, there is a problem when the system tries to start NetServer which causes the system to lock-up. There is a database that contains what you want to be served by LDAP. > QZLSSERVER > 2. Display/alter/dump 2. Java time stamps are used for this comparison, so it is. No new Verify that the system has started the QZLSSERVER job within QSERVER. While using the Network Authentication Service wizard or when you are managing network authentication service properties in System i Navigator, you might encounter these errors. This is because the NetServer code swaps to the QSECOFR profile before issuing the command to end the QZLSSERVER job. . The QZLSSERVER job and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete processing. The cause of the problem is a memory leak in the EIM/LDAP code. My > systems both have unique names and domains. 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. . Használja a Work with TCP/IP Network Status (NETSTAT *CNN) parancsot annak ellenőrzéséhez, hogy a következő bejegyzések megjelennek-e a NETSTAT kimeneti fájlban. 10 - Unable to retrieve host IP address because of return code 3. The IBM i NetServer QZLSSERVER job experiences high paging levels when SMB2 is in use. 7. a hardcoded value which is in CSID 37. 3 - Exchange user profile failed. Verify that the system has started the QZLSSERVER job within QSERVER. I assume it's trying to figure out what IP address to bind too or something. 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. WelcometoPowertechPowertechExit PointManagerforIBMi 8 WhatisPowertechPowertechExit PointManager? 9 PowertechPowertechExitPoint. To start: The method that is used to start the server. 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. Write down the. Tom - I have a 170 running V5R1M0 with 5722999 (Licensed Internal Code) cum TL02134 and 5722SS1(OS/400) cum TC02134. However, when I looked at the previous sign-on field on the user profile QSECOFR, it had not been used to sign onto our server for over three months prior to this incident happening, so that tells me that. 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. ). . If the QZLSSERVER job is not active, you must restart IBM i NetServer. . 3 - Exchange user profile failed. . . A Szerverek automatikus indítása paraméter szállított alapértelmezett értéke: Az IBM i számos szerverhez alapértelmezett Szerverek automatikus indítása paraméter értékeket tartalmaz. QHTTPSVR/QZHBHTTP. . If the QZLSSERVER job is not active, you must restart IBM i NetServer. Activation Instructions None. 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. 1. Select Option 10 for the joblog. The current search engine is no longer viable and we are researching alternatives. Verificaţi dacă sistemul a pornit jobul QZLSSERVER în cadrul QSERVER. The QZLSSERVER job and QZLSFILE jobs may 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. code is changed to the job CCSID before a comparison is made. Resolving The Problem. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. RE: NetServer Not Starting -- Find the NetServer host job (QZLSSERVER) and see if it shows anything helpful. Malwarebytes shows clean (as far as network staff can tell). . CIRCUMVENTION FOR APAR MA47776 :-----None. : Â The required iSeries NetServer job QZLSSERVER was unable Âto start because of reason code 13. '0' - Reset (0 indicated no reset)4 Answers. a hardcoded value which is in CSID 37. We can assume that the iSeries NetServer server (QZLSSERVER) job is up and running since your user can connect to the share. Cause . Eg: QMGR A has several QMGRS(B,C,D,E,F. Network Security uses several exit programs that interact with the various servers on IBM i. 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. . The cause of In IBM Navigator for i, for the system in question, navigate to IBM i Management -> Network -> Servers -> TCP/IP, right click on IBM i NetServer, and select Properties. CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER from ending has been removed. 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. To display the contents of the history log QHST, complete the following steps: Type DSPLOG (the Display Log command) on the command line. 2 - Unable to retrieve credentials. 3. You need to set that up before it can serve it. If root cause is to be determined, the following diagnostic materials must be gathered before any recovery action is taken. . Neil wrote: >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. 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. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem.