Make sure that z/OS UNIX is customized to be able to start automatically
during IPL.
If you want to use the z/OS NFS server, TCP/IP and PORTMAP need
to be started and active on your system. Then, start the z/OS NFS
server.
You might also need to start up NAMESRV to map machine names into
their corresponding Internet addresses. If you use the dynamic host
configuration protocol (DHCP), NAMESRV is required.
Note: - PORTMAP is synonymous with portmapper, which is a program provided
by z/OS Communications Server that maps registered server programs
to port numbers. NAMESRV is the cataloged procedure of the Domain
Name Server which is provided by Communications Server that maps a
host name to an internet address or an internet address to a host
name. See z/OS Communications Server: IP Configuration Guide and z/OS Communications Server: IP Configuration Referencefor information on configuring
PORTMAP, starting PORTMAP, configuring the Domain Name Server, and
starting NAMESRV automatically with z/OS Communications Server.
- The z/OS Portmapper does not support IPv6. Therefore, when using
IPv6 addresses, the z/OS server host must be configured with RPCBIND,
not the Portmapper. RPCBIND supports both IPv6 and IPv4. As of z/OS
V1R8, Portmapper should only be used for IPv4 only systems. Otherwise,
RPCBIND should be used.
The z/OS NFS server does not support file persistence. That is,
when the server is restarted, files cannot be accessed using old file
handles.
To start the z/OS NFS server, enter the start command
from a console. Enter the command as follows:
>>-START--mvsnfs------------------------------------------------>
>--+---------------------------------------------------------------------------+-->
| .-info--. |
'-,parms='-+-error-+-+---------+-+------------+-+----------+-+----------+-'-'
'-warn--' '-,altsym-' '-,ctrace=nn-' '-,dsps=nn-' '-,version-'
>--+---------------------------+-------------------------------><
| .-ignore-. |
'-',startfail=-+-dump---+-'-'
where
- mvsnfs
- Specifies the name of the procedure in your system PROCLIB used
to start up the server.
- info
- The first parameter specifies the level for diagnostic messages
(the default is info).
- altsym
- If altsym is specified in the second parameter, the
semicolon (;) is used as the comment symbol in the attributes (with one exception: If the fn_delimiter(;) attribute
uses a semicolon, the fn_delimiter semicolon is treated as a delimiter
between the file name and the attributes that follow, not as a comment
symbol) and exports data sets. Otherwise, the pound sign (#)
is used as the comment symbol.
For example, suppose you have some
data sets with a high-level qualifier of #USER05, and you
want client users to be able to read them. First, you would modify
the exports data set and attributes data set by using ‘;’
as the comment symbol rather than ‘#’. Next you would specify #user05
-ro as an entry in the exports data set. Finally, you would
specify the altsym parameter when you enter
the start command.
- ctrace=nn
- Specifies that diagnostic information for the NFS server be
recorded in z/OS component trace buffers, using trace options specified
in member CTINFSnn of SYS1.PARMLIB. To
use the default trace options for the z/OS NFS server, specify ctrace=00 for
the default SYS1.PARMLIB member CTINFS00. If the ctrace operand
is not specified, then the default SYS1.PARMLIB member CTINFS00 is
used.
- dsps=nn
- Specifies the size of the data space to be allocated
for the NFS component trace buffers, where nn equals the
number of megabytes to be allocated for each trace buffer. NFS uses
3 trace buffers in rotation. The value of nn can be between
10 and 600. If a value outside this range is specified, it will be
adjusted accordingly. The default value is 10 (representing 10 MB).
- version
- Causes the server to place a GFSA947I message on behalf of each
module in the server into the server log and component trace, at startup.
Similar to using the MODIFY mvsnfs, version=all operator
command.
- startfail
- Specifies the action the z/OS Network File System Server should
take if it encounters a terminating error during startup, or later
during execution which did not otherwise create a dump.
- ignore: No special action is taken. The
z/OS Network File System server proceeds with termination as it has
done prior to z/OS NFS V1R11. This is the default setting if the parameter
is not specified.
- dump: For terminating errors, an SVC dump
is created before terminating, if no dump was otherwise created.
Note: No dump is produced if the z/OS Network File
System server is stopped by the operator stop request. A dump is
generated if the z/OS Network File System server shuts down because
of a TCP/IP termination.
These parameters override the parameter settings in the server
startup procedure.
When you enter start, the following
console message appears; if you installed HDZ221N,
then this FMID is displayed in the GFSA348I message text.
GFSA348I z/OS NETWORK FILE SYSTEM SERVER
(HDZ221N, HDZ221N) STARTED.