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

Examples
Files
new zFS or HFS file system. Typically, one allocation error value and
reason code is displayed for the last allocation error, if there was one. If a
zFS file system could not be created, you will see message text or error
and reason codes (or both) for each automount-managed directory where
the zFS file system was to be created.
–q Displays the current automount policy. –q is mutually exclusive with –a.
–s Checks the syntax of the configuration file. No automount is performed.
1. The following example shows how automatic unmount can be avoided for a
directory:
name wjs
duration nolimit
Keywords that are not specified on a specific entry are inherited from the
generic entry, if present. If the generic entry is not present, or if keys are not
specified, the defaults are used. If the filesystem key cannot be resolved, the
entry is considered invalid.
2. The following is an example of a /etc/auto.master file that is used to specify /u
as automount-managed and the specifications for that directory in /etc/u.map:
/u /etc/u.map
automount uses these files:
/etc/auto.master
Specifies a list of directories to be configured, along with their MapName
files.
Each line in this file contains two pathnames separated by at least one
space: the directory name to be managed and the pathname of the
MapName file. Both of these pathnames should be absolute.
The pathname of the managed directory is used as a file system name
prefixed with *AMD. This restricts the length of the pathname of a managed
directory to 40 characters. If pathnames need to be longer, you can use
symbolic links to resolve all or part of the pathname.
Blank lines and lines beginning with the characters /* are considered
comments and are ignored. Line comments are not tolerated
MapName
The MapName file contains the mapping between a subdirectory of a
directory managed by automount and the mount parameters.
The file is organized as a set of specifications. Each specification contains
one or more lines. Each line is of the form keyword argument. Each
specification must begin with the keyword name.
Blank lines and lines beginning with the characters /* are considered
comments and are ignored. Line comments are not tolerated
A generic entry can be specified as the first specification by using the name
of *. The generic specification provides defaults for subsequent specific
specifications. When the automounter tries to resolve a lookup request, it
attempts to find a specific entry. If a specific entry does not exist for the
name being looked up, it attempts to use the generic entry.
The following is an example of a generic entry:
automount
Chapter 2. Shell command descriptions 27