Mount examples

Table 1 shows how to mount z/OS MVS data sets from various platforms.

Table 1. Examples of mounting MVS data sets from clients
Clients	Command Examples
UNIX	mount -o vers=n,sec=r,proto=x mvshost1:"MVSHLQ,procattr1,procattr2,...." /u/smith/mnt
Linux (NFS version 4)	mount -t nfs4 -o sec=r,proto=x mvshost1:MVSHLQ /u/smith/mnt Note: For NFS version 4 mounts to the z/OS NFS Server, it is recommended to use the "nordirplus" mount option from Linux NFS Clients.
Linux (NFS version 2 and 3)	mount -o vers=n ,proto=x mvshost1:MVSHLQ /u/smith/mnt
Windows	nfs link z:"\\mvshost1\MVSHLQ,procattr1,procattr2,..." id pw
Any (UNIX, Linux, Windows), with explicit MVS prefix	mount ... mvshost1:"/mvs/MVSHLQ"...

In the examples:

Operand: Description
mvshost1: Specifies the name of the z/OS host.
/mvs: Assuming that MVSPREFIX(/mvs) is set in the site attribute file (this is the default), identifies this as an MVS mount. Note that this does not need to be /mvs. It only needs to match the MVSPREFIX value (case-insensitive).
MVSHLQ: Specifies the high-level qualifier of the MVS data set.
procattr: Specifies any valid processing attribute, such as text/binary or hfsfbtimeout(n).
/u/smith/mnt: Specifies the local mount point.
z:: Specifies the drive letter on the Windows system.
id pw: Specifies login id and password for pcnfsd.
-t nfs4: Specifies NFS protocol version 4 for Linux (optional).
-o vers=n: Specifies the NFS protocol version to be used (2 or 3 for Linux; 2, 3 or 4 for others) (optional).
-o sec=r: Specifies RPCSEC_GSS security flavors, which is available only on the z/OS NFS version 4 server. Valid options are sys, krb5, krb5i, and krb5p.
-o proto=x: Specifies the transport protocol for the NFS client to communicate with the NFS server. Valid options are tcp or udp. (Note for IPv6, some platforms use proto=tcp6 instead of tcp)