Starting the z/OS NFS client

If you want to use the z/OS NFS client, do the following:

Define the z/OS client as a file system in the z/OS UNIX BPXPRMxx member of SYS1.PARMLIB. Start the z/OS UNIX address space, which will cause the BPXPRMxx member to be used. As part of the z/OS UNIX startup, the z/OS NFS client will be started in an z/OS UNIX colony address space. Wait until this message appears before proceeding:
```
 BPXI004I OMVS INITIALIZATION COMPLETE
```
See z/OS UNIX System Services Planning for more information.
Ensure that TCP/IP and PORTMAP are active.

During z/OS UNIX file system initialization, the z/OS NFS client is started and run in the z/OS UNIX colony address space. The FILESYSTYPE parmlib statement for the z/OS NFS client must be present in the SYS1.PARMLIB(BPXPRMxx) parmlib member in order to start the z/OS NFS client. BPXPRMxx can specify optional component trace options for the NFS client, as shown in Using NFS component trace PARMLIB members CTINFSnn and CTINFCnn. For more information on z/OS UNIX file system, see z/OS UNIX System Services File System Interface Reference.

If the z/OS NFS client fails to initialize, a write to operator (WTO) message is issued to the operator console. The following conditions can cause z/OS NFS client initialization to fail.

The z/OS NFS client is not started in a standalone colony address space.
The z/OS NFS client is already started. Multiple instances of the z/OS NFS client on a single z/OS system is not supported.
Using a security product that is downlevel, the z/OS NFS client requires RACF® 2.2 or later.
An incorrect parameter is specified in the installation parameters.
Unicode services is not installed or is not active.

When the z/OS NFS client initializes, messages like these example messages are displayed on the operator's console.

$HASP373 NFSCR    STARTED
BPXI004I OMVS INITIALIZATION COMPLETE
GFSC700I z/OS NETWORK FILE SYSTEM CLIENT
(HDZ221N) started. HDZ221N, GFSCMAIN, Jun 14 2012  15:29:05.

If the z/OS NFS client is stopped, canceled, or for any other reason terminates, z/OS UNIX issues the following message:

BPXF032D FILESYSTYPE type TERMINATED. REPLY 'R' WHEN READY TO RESTART.
          REPLY 'I' TO IGNORE

To restart the z/OS NFS client, specify 'R' in reply to the message. Replying with 'I' will cause z/OS UNIX to ignore the termination of the z/OS NFS client. If 'I' was replied and you still wish to restart the z/OS NFS client, use the SET command as follows. If z/OS UNIX has been initialized but the z/OS NFS client is not active, issue a SETOMVS RESET=(xx) command to the BPXPRMxx member of SYS1.PARMLIB that defines the z/OS NFS file system. z/OS UNIX will then start the z/OS NFS client.