Mount examples

Table 1 shows how to mount z/OS UNIX files from various platforms.
Table 1. Examples of the mount command for clients
Clients Command Examples
AIX, UNIX/Linux, Solaris mount -o vers=n,sec=r,proto=x mvshost1:"/hfs/smith" /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 Redhat EL 5 (NFS version 4 only) mount -t nfs4 -o sec=r,proto=x mvshost1:"/hfs/smith" /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.
Windows mount \\mvshost1\hfs\smith z:
Any (UNIX, Linux, Windows), with implicit prefix mount .... mvshost1:/smith ....

In the examples:

Operand
Description
mvshost1
Specifies the name of the MVS host.
/hfs
Specifies the HFS prefix. Note that the HFS Prefix is not required, depending on the implicit prefix selection algorithm specified in the IMPPREFIX site attribute.
/smith
Specifies the HFS directory to be mounted.
/u/smith/mnt
Specifies the local mount point.
-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 the mount security flavors. Valid options are sys, krb5, krb5i, and krb5p. Kerberos RPCSEC_GSS security flavors (krb5, krbpi, krb5p) are only supported by the z/OS NFS Server on NFS version 3 and NFS version 4 mounts.
-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)
Note:
  1. The /hfs prefix value is used by the z/OS NFS server to determine if a file is a z/OS UNIX file, and does not appear in the path name of an HFS file once it is mounted.
  2. The HFS prefix is not required, depending on the implicit prefix selection algorithm specified in the IMPPREFIX site attribute.