Open System Services NFS Management and Operations Guide

1. Stop any LAN interface processes that are still running.
2. Run the port mapper (if it is not already running).
3. Run the OSS NFS manager process.
4. Issue the SCF START SUBSYS command.
5. Run the PCNFSD process.
Examples
• You can restart OSS NFS directly:
STOP $LAN0
VOLUME $SYSTEM.ZOSSNFS
RUN $SYSTEM.ZRPC.PORTMAP &
/NAME $ZPM0, PRI 148, NOWAIT, CPU 1/0, TCPIP $ZTC0
RUN NFSMGR /NAME $ZNFS, NOWAIT/
RUN SCF /IN SCFIN/
RUN PCNFSD /NAME $PCD0, NOWAIT, IN ZPCDCONF/$SYSTEM.NFSCONF
In this example, SCFIN should contain commands for configuring objects and starting the
processes, as described in:
◦ “Configuring OSS NFS Objects” (page 41)
◦ “Starting OSS NFS” (page 52)
◦ “Adding a LAN Interface Process” (page 49)
◦ “Starting PCNFSD” (page 49)
• The NFSWARM file, generated by the NFS SETUP program, can also be used to restart OSS
NFS:
VOLUME $SYSTEM.NFSCONF
RUN NFSWARM
Verifying OSS NFS Connectivity
After the OSS NFS subsystem is configured and running, you should check whether you have
end-to-end connectivity between your client systems and OSS NFS by using the RPCINFO program.
The RPCINFO program is invoked by issuing the following TACL command.
[ ADD DEFINE=ZRPC^RPC^FILE, FILE rpc-file ]
[ ADD DEFINE=TCPIP^HOST^FILE, FILE file1 ]
[ ADD DEFINE=TCPIP^RESOLVER^NAME, FILE file2 ]
[ ADD DEFINE=TCPIP^PROCESS^NAME, FILE process ]
[\system.]RPCINFO -p [ host-name ]
FILE rpc-file
specifies the name of the RPC program definition file, which contains a list of well-known RPC
programs that correspond to RPC program numbers. This file is typically located at
$SYSTEM.ZRPC.RPC; if it is not, you must supply this DEFINE.
Verifying OSS NFS Connectivity 53