Mount processing parameters and installation parameters

Table 1 shows the client attributes that can be modified when used as parameters on the MOUNT command.
Table 1. Mount processing parameters
Mount processing parameters
acdirmax(n)
accesschk(Y|N)
acdirmin(n)
acregmax(n)
acregmin(n)
attrcaching(Y|N)
cln_ccsid(n)
convserv(UNICODE technique)
datacaching(Y|N)
delaywrite(n)
delim (na|binary|nl|cr|lf|crlf|lfcr)
dynamicsizeadj(Y|N)
hard|soft
llock(Y|N)
proto(tcp|udp)
public
readahead(n)
retrans(n)
retry(n)
rpcbind(Y|N)
rsize(n)
secure(krb5|krb5i|krb5p|udp)
stringprep(Y|N)
srv_ccsid(n)
syncwrite(Y|N)
timeo(n)
vers(2|3|4)
wsize(n)
xlat(Y|N)
Table 2 shows installation parameters.
Table 2. Installation parameters
Installation parameters
attrcaching(Y|N)
biod(n)
bufhigh(n)
cln_ccsid(n)
convserv(UNICODE technique)
datacaching(Y|N)
delaywrite(n)
delim (binary|nl|cr|lf|crlf|lfcr)
disablella(Y|N)
dynamicsizeadj(Y|N)
llock(Y|N)
mtxtonly
readahead(n)
rpcbind(Y|N)
secure(krb5|krb5i|krb5p|udp)
srv_ccsid(n)
stringprep(Y|N)
syncwrite(Y|N)
xlat(Y|N)

The following conditions may cause the NFS client to fail its initialization:

  • The NFS client is not started in a stand-alone colony address space.
  • The NFS client is already started; multiple instances of the NFS client on a single z/OS system are not supported.
  • Invalid parameter is specified in the installation parameters.
  • If Unicode exists, then Unicode is used. If Unicode does not exist and Character Data Representation Architecture (CDRA) exists, then CDRA is used. If both Unicode and CDRA do not exist, then initialization fails.

A WTO message is issued to the operator console if the NFS client fails to initialize.