Technical data

MOUNT
With NONUNIQUE, the client uses the file handle instead of the file ID. This
can refresh directory entries in the client’s cache more quickly. However, this can
degrade performance because the client must issue additional RPC requests to
get the file handle.
/FORCE
/NOFORCE
Optional. Default: /NOFORCE.
Performs an overmount or a mount that can cause file system occlusion.
Required privileges:
• OPER
• SYSPRV (for overmounting a /SYSTEM mount)
• GRPNAM (for overmounting a /GROUP mount)
/GID=n
Optional. Default: –2.
Default GID if no GID mapping exists for file access.
Restriction: Requires OPER privilege.
/GROUP
Optional. Default: User mounted.
Adds the logical name to the group logical name table. If the mount is the first
one on the volume, /GROUP marks the volume as being group-mounted.
Restrictions:
• Requires GRPNAM privilege.
• /GROUP and /SYSTEM are mutually exclusive.
/HOST=host
Required.
Remote NFS server on which the physical files reside. Type either domain-name
or IP-address format.
/OWNER_UIC=n
Optional. Default: Ownership recorded on the volume.
UIC-assigned ownership of the volume while you mount it.
Applied only on the first mount of an NFS disk.
/PATH="/path/name"
Required.
Path name on the NFS server (specified by /HOST). Must match an exported
directory, subdirectory, or file of an exported file system on the server.
The /path/name is mounted as the master file directory (MFD) of the specified
device.
/PROCESSOR= {UNIQUE | SAME:DNFSn: | FILE:file}
Optional. Default: New ACP for each mount.
2–68 Command Descriptions