Troubleshooting file share problems

If you experience problems with IBM i NetServer file share readiness, check the status of IBM i NetServer on the system.

1. Verify that the system has started the QSERVER subsystem.
   If the system has not already started the QSERVER subsystem, then start it by using the Start Subsystem (STRSBS) CL command.
2. 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.
3. Verify that the QZLSFILE prestarted job is waiting for a program start request (PSRW status on the Work with Active Jobs display).

   If threaded support is required, verify that the QZLSFILET job is awaiting client requests for file or print serving (TIMW or TIMA status on the Work with Active Jobs display).

   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 threadsafe file shares. 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 NetServer. However, if not running threaded, Linux connects to a separate QZLSFILE job for each mount of an IBM i 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.