Troubleshoot iSeries NetServer file share problems

If you experience problems with iSeries NetServer™ file share readiness on iSeries, then you should check the status of iSeries NetServer on iSeries. To do so, follow these steps:

1. Verify that iSeries has started the QSERVER subsystem. If iSeries has not already started the QSERVER subsystem, then start it by using the Start Subsystem (STRSBS) CL command.
2. Verify that iSeries has started the QZLSSERVER job within QSERVER. If iSeries has not already started the QZLSSERVER job, then start it by using the STRTCPSVR *NETSVR CL command.
3. Verify that the QZLSFILE prestarted job is waiting for a program start request (PSRW status on the Work with Active Jobs screen). If threaded support is desired, verify that the QZLSFILET job is awaiting client requests for file or print serving (TIMW or TIMA status on the Work with Active Jobs screen). If neither the QZLSFILET nor a QZLSFILE prestarted job is waiting for a program start request, then use the Start Prestart Jobs (STRPJ) CL command. This starts the prestarted job.
   Note:
   If a subsystem is configured to start the QZLSFILET job, that single QZLSFILET job services multiple clients and their respective thread-safe file shares. There are multiple QZLSFILE jobs in a subsystem and each one supports one client and all of the non thread-safe file shares that are accessed by a Windows client when using iSeries NetServer. However, if not running threaded, Linux connects to a separate QZLSFILE job for each mount of an iSeries NetServer share.
   
4. Add the QZLSFILET or QZLSFILE prestarted job to the QSERVER subsystem description (or a different subsystem description if you have configured others) if it is not already present. You can use the Add Prestarted Job Entry (ADDPJE) CL command to add the prestarted job entry.

For more information on threaded client activity and problems that may be encountered, see Troubleshoot iSeries NetServer user profile connections.