Verificaţi dacă sistemul a pornit jobul QZLSSERVER în cadrul QSERVER. The msgMCH6906 messages occur up to 10 times per second and cause the joblog to wrap. Activating Powertech Network Security. 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. 2 - Unable to retrieve credentials. Verificaţi dacă job prestart QZLSFILE aşteaptă o cerere de pornire a programului (starea PSRW despre lucrul cu afişarea joburilor active. The QZLSSERVER is automatically started every time the QSERVER subsystem is started. The security auditing function must be set up before you can use this command. To prompt the command, select F4. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. Regards, Simon Coulter. Starting AS/400 NetServer starts QZLSSERVER and the four (4) Netbios connections can be seen in NETSTAT *CNN, but this lasts just 30 seconds. The internal search function is temporarily non-functional. . Enter the command to start iSeries Netserver. . The current search engine is no longer viable and we are researching alternatives. : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 5. CORRECTION FOR APAR MA47776 :-----While ending TCP/IP, the timing window causing the hang that prevents QZLSSERVER. . Problem Conclusion. 215. The NetServer QZLSSERVER job starts using CPU over a period of time and the CPU keeps increasing each day until an IPL. The major issue was that the upgrade recycled QSERVER and ended some jobs from QUSRWRK. 1. 3 - Exchange user profile failed. * * netbios > 001:27:44 ListenCause . From the character based interface: Type CHGxxxA at the i5/OS command line, where xxx is the name of the server. For the servers to use the exit programs, the exit programs must be registered. . . 23 is invalid. 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 following tools might help you a bit as well, at least at the iSeries end:Look for the QZLSSERVER job in the QSERVER subsystem. If the QZLSSERVER job is not active, you must restart IBM i NetServer. Resolving The Problem. Accès QDLS, IFS et OS400 V5. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. 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. . . . The following describes the parameters and allowable values for each field on the Work with Activation panel. meanwhile, maybe check your subsystem jobs (detail of the "Start of prestart. . The internal search function is temporarily non-functional. . The IBM i NetServer QZLSSERVER job experiences high paging levels when SMB2 is in use. . QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. 3 - Exchange user profile failed. The QZLSSERVER job is in the QSERVER subsystem. . : QPGMRQZLSSERVER is IBM Net Server. ). QZLSSERVER Joblog 1. My old computer, win2k, has no problems. . If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 13. will be corrected so that the hard coded value in the kerberos. . ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT. The QZLSSERVER job and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete internal processing. Recovery . iSeries NetServer is not properly cleaning up unprocessed client requests which causes iSeries NetServer to not end. 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. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 6. When you configured Netserver using the wizard, did you specify a WINS server?Használja a Work with Active Job (WRKACTJOB) parancsot annak ellenőrzéséhez, hogy fut-e a QZLSSERVER nevű job a QSERVER alrendszer alatt. For the servers to use the exit programs, the exit programs must be registered. Activating Powertech Network Security. 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. 2 - Unable to retrieve credentials. start because of reason code 6. 1. 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. 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. After starting QSERVER, delay 60 seconds (this value has. Network Security uses several exit programs that interact with the various servers on IBM i. NetServer mapped drive access becomes slower and slower until they reach a point where they are unusable. 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. It is not possible to determine what is causing the profile to be disabled for NetServer; however, the message that is generated (message CPIB682) does provide the IP address of the computer where the profile was disabled. The internal search function is temporarily non-functional. Default InstructionsVerify that the system has started the QZLSSERVER job within QSERVER. You need to set that up before it can serve it. This CPU increase is associated with heavy use of the NetServer network printing function. . . . 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. 3 - Exchange user profile failed. Internet Daemon (INETD) SuperServer. The password is the administrator password for the instance. . Sorted by: 62. See the following reason codes and their. To start NetServer, type STRTCPSVR *NETSVR and then DSPMSG QSYSOPR to verify. 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. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). 3 - Exchange user profile failed. Somewhere in the Netserver configuration dialog is a tab or dialog to show disabled users and allow them to be enabled. . . : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 6. We can assume that the iSeries NetServer server (QZLSSERVER) job is up and running since your user can connect to the share. 2 - Unable to retrieve credentials. The Start Server (QZSLSTRS) and End Server (QZLSENDS) APIs start and end the server. Verify that the system has started the QZLSSERVER job within QSERVER. Resolving The Problem. If "Include LIB" is set to Y, it includes the QUSRDIRDB, QUSRDIRCF, and QUSRDIRCL library saves. (I don't have access to it on our systems, so I can't be more specific. This. . I assume it's trying to figure out what IP address to bind too or something. . the values do not match because of the CCSID difference. CIRCUMVENTION FOR APAR MA47776 :-----None. 11. Using the Work with TCP/IP Network Status (NETSTAT *CNN) command, the following entries are shown. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. This basically serves up shares on your IBM i. Solution 2: Make sure the EIM domain controller password matches the LDAP administrator password. Verify that the system has started the QZLSSERVER job within QSERVER. . . DSPLOG QHST JOB(QZLSSERVER) Press the Enter key. 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. or DDM Connection fails with message CPD3E3F when connecting to target IBM i:CPD3E3F. Network authentication service Network authentication service allows the iSeries ™ server and several iSeries services, such as iSeries Access for Windows ®, toVerify that the system has started the QZLSSERVER job within QSERVER. DDM Connection hangs logging message MCH3601 in the joblog when connecting to target IBM i:MCH3601 - Pointer not set for location referenced. . If the QZLSSERVER job is not active, you must restart IBM i NetServer. It determines if the job was used at least twice within the maximum job monitor interval length. . 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. Activating Powertech Network Security. If the password is unknown, leave it blank. Cause . 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. 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. Press the Enter key. The current search engine is no longer viable and we are researching alternatives. The Open List of Server Information (QZLSOLST) API opens a list of information about the server for share, configuration, session, statistics, or connection information. 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. . The internal search function is temporarily non-functional. 2 - Unable to retrieve credentials. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. The help for that message only adds some. If the QZLSSERVER job is not active, you must restart IBM i NetServer. It is important to "salt" the password, to defend oneself against rainbow table attacks. Solution 2: Make sure the EIM domain controller password matches the LDAP administrator password. 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 . For the servers to use the exit programs, the exit programs must be registered. 7. . WRKACTJOB JOB(QZLSSERVER) If a job is displayed, the server is active. . Cause . : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 13. CIRCUMVENTION FOR APAR MA47776 :-----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. CWBSY1018 RC613. Tom - I have a 170 running V5R1M0 with 5722999 (Licensed Internal Code) cum TL02134 and 5722SS1(OS/400) cum TC02134. 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. You simply need to update the host table and/or DNS entry and may even be a WINS entry. . 22,PowertechExitPointManagerwasnamedPowertechNetwork. If you have to ask what LDAP is, then you do not need to start *DIRSRV at this time. Steven Segars. 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 and QZLSFILE jobs may remain in END status and cannot be terminated by the user until they complete internal. . . In System i Navigator go to Netowkr --> Enterprise Identity Mapping and right click on 'Configuration' and click on 'Properties'. RE: NetServer -- Thanks Chris for this information. The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. In a cluster environment , I see channels to a particular server is ending abnormally and resuming frequently in a day. For example, CHGFTPA to work with the attributes of the FTP server. There doesn't seem to be an explanation of return code 3. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). Por eso no es necesario realizar ningún cambio en el programa de arranque si el subsistema QSERVER se inicia antes de que se inicie TCP/IP. . IBM Tivoli Directory Server: LDAP: WRKACTJOB JOB(QUSRDIR) If a job is displayed, the server is active. CORRECTION. The Start Server (QZSLSTRS) and End Server (QZLSENDS) APIs start and end the server. a hardcoded value which is in CSID 37. 4 - Unable to obtain lock for service program QZLSSRV1 in library QSYS. 4 - Unable to obtain lock for service program QZLSSRV1 in. The internal search function is temporarily non-functional. As an. 2 - Unable to retrieve credentials. Impact of recycling QSERVER, some QUSRWRK jobs -- Completed the Netiq PSAUDIT/PSSECURE 8. Dump to printer 2. . 2 - Unable to retrieve credentials. The QZLSSERVER is automatically started every time the QSERVER subsystem is started. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. -----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 - Contact your service provider. 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. 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. Activating Powertech Network Security. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. If the QZLSSERVER job is not active, you must restart IBM i NetServer. You can view that QZRCSRVS joblog to. Profile is not disabled. : Complete recovery for the specified reason code. Special Instructions None. 3 - Exchange user profile failed. See reason 1 shown below: 1 - The End Prestart Job. However, the QZLSSERVER job did not end, which caused iSeries NetServer not to start. The QZLSSERVER job is in the QSERVER subsystem. Look for the QZLSSERVER job. 13 - Correct the name configured for IBM i NetServer which. 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. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. . LIC-OTHER INTERNAL EXTENSIONS FOR MAINTAINABILITY [{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM. . . If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. have you put on any latest patches on your computer. 3 - Exchange user profile failed. Problem Conclusion. CALL QZLSCHSN PARM(server-name domain-name 'text description or comment' X'00000000') After you change the IBM i NetServerserver name, you should add it to the Domain Name System (DNS) or to your PC client's LMHOST file. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. 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. . 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. 2 - Unable to retrieve credentials. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. To display these options, from the Network Security Main Menu, select option 81, Configuration Menu. 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. . This causes a problem as the QZLSSERVER job won't start on > my backup box until I go into Operations Navigator and manual change > the server name and domain name to what they are suppose to be. In IBM i Navigator, navigate under the system in question to Network -> Servers -> TCP/IP, right click on IBM i NetServer, and select Properties. No particular advice on the two jobs. QZLSSERVER *YES: 137 TCP (netbios-ns) 137 UDP (netbios-ns) 138 UDP (netbios-dgm) 139 TCP (netbios-ssn) 445 TCP (cifs) IBM i NetServer. Because of this, no changes are needed in your startup program if the QSERVER subsystem is started before TCP/IP is. When Netserver starts, it sends out a DNS query for it's assigned name. Post by comp. 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. o: TCP/IP must be active. 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. the values do not match because of the CCSID difference. 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. . 3 - Exchange user profile failed. 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. 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. CORRECTION FOR APAR MA46670 :-----An internal heap allocation used by IBM i NetServer for Query Directory operations is much larger than necessary. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. Verify that the system has started the QZLSSERVER job within QSERVER. . Work with Exit Point Manager Activation. 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. If QZLSSERVER is not active, then NetServer is not started. All from 11/07/03. Share This. User Defined Subsystem Support Accounting runs here Sales team runs hereQZLSSERVER MCH6903 - 5770 sp/qgldheap mod/qgldheap. Problem Conclusion. Ověřte, zda již systém spustil úlohu QZLSSERVER v subsystému QSERVER. If the system has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command. NetServer mapped drive access becomes slower and slower until mapped drive access reaches a point where it is unusable. Use the WRKSBS command to confirm that the Qserver subsystem is started. Cause . Select a “Job name” of QZLSSERVER (iSeries Netserver’s job name on the iSeries). . See the following reason codes and their meanings: . Network Security uses several exit programs that interact with the various servers on IBM i. FTP SSL problems with large files, no problem with standard FTP. Our Network and AS/400 User-ID's are not the same, so I had the same problem. To display the contents of the history log QHST, complete the following steps: Type DSPLOG (the Display Log command) on the command line. 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. . . Provjerite da je sistem pokrenuo QZLSSERVER posao unutar QSERVER. 1. misc. See the following reason codes and their meanings: 13 - The retrieved host IP address of 6. To activate Powertech Exit Point Manager. . If root cause is to be determined, the following diagnostic materials must be gathered before any recovery action is taken. : The required iSeries NetServer job QZLSSERVER was unable to start because of reason code 13. : The required AS/400 NetServer job QZLSSERVER was unable to start because of reason code 12. 3 - Exchange user profile failed. 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. Our operators run a process each week day requiring from one to ten files on our IFS to be processed. . QZRCSRVS cleanup. On 26/08/2009, at 5:45 AM, Jerry Adams wrote: Any ideas what I should look for? Find the NetServer host job (QZLSSERVER) and see if it shows anything helpful. 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). 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). period of time to end. For example, the following DSPOBJD. Cause . The Network Security activation process uses the Add Exit Program (ADDEXITPGM) command to add the exit programs to the system registry. Check for a QZLSSERVER job log: WRKJOBLOG JOBLOGSTT(*PENDING *SPOOLED) JOB(QZLSSERVER) Check the QEZDEBUG output queue for any dumps or logs created by this job. See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. . Go back to option 12 and change the lookup priority from *REMOTE to *LOCAL, and doCause . 1. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. The Start Server (QZSLSTRS) and End Server (QZLSENDS) APIs start and end the server. . Using the Work with TCP/IP Network Status (NETSTAT *CNN) command, the following entries are shown. Verify that the QZLSFILE prestarted job is waiting for a program start request ( PSRW status on the Work with Active Jobs display). A cleanup thread runs once an hour to determine whether a QZRCSRVS job is still being used by a Job Monitor. Pentru pornire:Verify that the system has started the QZLSSERVER job within QSERVER. See the following reason codes and their meanings: 1 - NETBIOS over TCP/IP started with errors - return code 0. QSYS/QTOINETD. : The required IBM i NetServer job QZLSSERVER was unable to start because of reason code 5. . Activating Powertech Network Security. Use the Work with Active Job (WRKACTJOB) command to verify that there is a QZLSSERVER job running under the QSERVER subsystem. 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. Cause . . Dump to printer 2. 2 - Unable to retrieve credentials. You can track this item individually or track all items by product. . See the following reason codes and their meanings: 1 - Unable to retrieve user credentials. 4 - Unable to obtain lock for service program QZLSSRV1 in. CPF0920 All prestart jobs for program QZLSFILE in library QSYS in subsystem QSERVER are ending for reason 1. 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. DSPLOG QHST JOB(QZLSSERVER) Press the Enter key. Cause . There is no problem from the users standpoint, they are not denied access. Expand Shared Objects and right-click on the share name to select Permissions. 2 - Unable to retrieve credentials. To display the contents of the history log QHST, complete the following steps: Type DSPLOG (the Display Log command) on the command line. 0. Activating Powertech Network Security. IBM i NetServer jobs will, on rare occasion, take an extended period of time to end. . . You can track this item individually or track all items by product. 13 - The retrieved host IP address of 209. · The NETSERVER job is startedCheck for a job named QZLSSERVER. . This. ; Use the Work with TCP/IP Network Status (NETSTAT *CNN) command to verify that the following entries appear in the NETSTAT.