z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

MOUNT
Usage notes
AUTOMOVE(EXCLUDE,sysname1,sysname2,...,sysnameN) or
AUTOMOVE(E,sysname1,sysname2,...,sysnameN)
The EXCLUDE indicator with a system list provides a list of systems to
which the file system's ownership should not be moved.
NOAUTOMOVE
NOAUTOMOVE prevents movement of the file system's ownership in some
situations.
UNMOUNT
UNMOUNT allows the file system to be unmounted in some situations.
Guidelines:
1. You should define your version and sysplex root file systems as
AUTOMOVE, and define your system-specific file systems as
UNMOUNT.
2. Do not define a file system as NOAUTOMOVE or UNMOUNT and a file
system underneath is as AUTOMOVE; in this case, the file system
defined as AUTOMOVE will not be recovered after a system failure until
the failing system is restarted.
For more information about shared file systems and the associated versions
and a sysplex root file systems, as well as details about the behavior of the
AUTOMOVE options, see z/OS UNIX System Services Planning.
1. The directory /samples contain sample MOUNT commands (called mountx).
2. When the mount is done asynchronously (NOWAIT was specified and return
code 4 was returned), you can determine if the mount has completed with one
of the following:
v The df shell command
v The DISPLAY OMVS,F operator command (see z/OS MVS System
Commands)
v The MOUNT table option on the File Systems pulldown in the ISPF Shell
(accessed by the ISHELL command)
3. In order to mount a file system as the system root file system, the caller must
be a superuser. Also, a file system can only be mounted as the system root file
system if the root file system was previously unmounted.
4. If you have previously unmounted the root file system, a ’dummy file system’ or
SYSROOT will be displayed as the current root file system. During the time
when SYSROOT is displayed as the root, any operation that requires a valid file
system will fail. When you subsequently mount a new root file system on
mountpoint /, that new file system will replace SYSROOT. When a new root file
system has been mounted, you should terminate any current dubbed users or
issue a chdir using a full pathname to the appropriate directory. This way, the
users can access the new root file system. Otherwise, an error will occur when
a request is made requiring a valid file system.
5. Systems exploiting shared file system will have I/O to an OMVS couple data
set. Because of these I/O operations to the CDS, each mount request requires
additional system overhead. You will need to consider the affect that this will
have on your recovery time if a large number of mounts are required on any
system participating in shared file system.
6. The TAG parameter is intended for file systems that don’t support storing the file
tag, such as NFS remote file systems.
836 z/OS V1R9.0 UNIX System Services Command Reference