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

|
|
|
|
|
|
Usage notes
value is not checked as being valid and the corresponding
code page is not checked as being installed.
For more information on file tagging, see z/OS UNIX
System Services Planning. Additional information about the
TAG parameter can be found in mount — Logically mount a
file system.
type The type of the file system (such as HFS, zFS, and NFS). The
default is HFS.
v When a new file system of the type HFS is created and allocated to a new user,
the owner UID and GID are based on that user. The setting of the permission
bits is 700.
v When a new file system of the type zFS is created and allocated to a new user,
the owner UID and GID are based on that user. The setting of the permission
bits is 750.
v The syntax of the automount master file is extended to optionally include the
name of the filter utility. Each line contains:
– The path name of the directory that is to be managed.
– The path name of the map file.
automount
– An optional path name of the conversion utility.
If a conversion utility is specified, automount will run that utility and provide the
specified map file as the standard input for the utility. It will process the utility’s
standard output as the automount map file and list it on its standard output.
Errors detected by automount will be flagged the same as before, but line
numbers will refer to the line as output from the conversion utility rather than the
original map file that the utility processes.
v Although automount ensures that loading a new policy is an atomic operation, it
does not serialize multiple simultaneous instances of running the automount
utility. This remains the case when using the -a option. This should not be used
in an automated script such as /etc/rc that can be run at the same time from
multiple systems. This may result in changes to the automount policy not being
done with no indication of this. When automount is run this way without the -a
option and the same policy is loaded from all systems, it is irrelevant that the
policy load from one or more systems is overlaid.
v automount recognizes the type specification in the automount map files of HFS
and zFS as potentially interchangeable file system types. At the time automount
applies the specification for the mount, it will determine if the file system is the
name of either an zFS or HFS file system and alters the type as appropriate. If
the data set does not exist and if allocany or allocuser is not specified, a new
file system is allocated as the file system type as specified in type. Allocation is
only done if allocuser or allocany is specified. If it is preferred to have new file
systems allocated as zFS file systems, the automount policy should be changed
to specify type zFS.
This allows automount managed file systems to be changed from HFS to zFS
without changing the file system name and without changing the automount
policy. If the file system name must be changed, it will be necessary to add a
specific entry in the automount policy for this file system or manage it on
another managed directory.
Chapter 2. Shell command descriptions 31