Mounting of MVS data sets onto a client mount point

To access an MVS file system from the client, you use the mount command to create a temporary link between specific MVS data sets and a UNIX directory (preferably empty) or an unused logical drive. The UNIX directory or drive is called a mount point.

You use an MVS high-level qualifier in the mount command to specify which MVS data sets to mount onto a mount point. The MVS data sets beginning with the specified high-level qualifier appear as files under the mount point. See Figure 1.

You can also perform a mount using a fully qualified partitioned data set name (PDS or PDSE) or an alias to a user catalog, but not the catalog name itself. Only cataloged data sets are supported by the z/OS NFS server, and tape data sets are not supported.

Data set organizations supported include:

Physical sequential (PS)
Direct access (DA)
Partitioned data sets (PDS)
Partitioned data sets extended (PDSE)
VSAM KSDS
VSAM ESDS
VSAM RRDS
SAM extended format data sets

Both SMS-managed and non-SMS-managed data sets are supported.

NFS supports multivolume data sets.
Generation data sets are not supported.

Note:

The filesize for the MVS z/OS conventional data set as a directory has a dummy size with a value of 8192.
For the NFS Version 3 CREATE procedure, the z/OS server does not harden the exclusive create verify token to disk.