z/OS Network File System Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


PARMLIB updates

z/OS Network File System Guide and Reference
SC23-6883-00

Add the data set defined in the GFSCPROC STEPLIB containing the z/OS NFS client library to the system's APF authorization list (IEAAPFxx). A sample cataloged procedure named GFSCPROC is provided as a member of the sample library NFSSAMP, see Sample z/OS NFS client startup procedures.

Add the filesystype parmlib statement shown in Figure 1 to the z/OS UNIX parmlib member (BPXPRMxx):

Figure 1. Sample filesystype parmlib statement
FILESYSTYPE
   TYPE(NFS)
   ENTRYPOINT(GFSCINIT)
   PARM('installation parms')
   ASNAME(proc_name)    

The name in the TYPE operand must be NFS, otherwise the utility program nfsstat fails.

The operand ENTRYPOINT(GFSCINIT) specifies the entry point for the z/OS NFS client initialization.

The operand PARM('installation parms') specifies the installation parameters for the z/OS NFS client. See Table 2 in Mount processing parameters and installation parameters for a list of valid installation parameters.

The operand ASNAME(proc_name) specifies the procedure name in SYS1.PROCLIB that is used by z/OS UNIX to start the address space in which the z/OS NFS client is initialized.
Note: The proc_name is also used for the name of the address space.

For data integrity and data isolation among different PFSs, the z/OS NFS client is required to start in a separate and standalone colony address space. To start the NFS client in a separate and standalone colony address space, a unique proc_name must be used.

For information about BSAM, QSAM, and VSAM ESDS files, see BSAM, QSAM, and VSAM ESDS access to remote files.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014