z/OS UNIX System Services Planning
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


MapName

z/OS UNIX System Services Planning
GA32-0884-00

The MapName file contains the mapping between a subdirectory of a directory managed by the automount facility and the mount parameters. It can contain both specific entries and a generic entry. When the automount facility 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 will then attempt to use the generic entry.

Tip: The MapName file can contain only one generic entry, and it has to be the first entry in the MapName file. When using generic entries, you should have a consistent naming criterion. The file system in Figure 1 has a high-level qualifier of OMVS, and the lower level qualifier is equal to the user ID.

Figure 1 shows an example of a MapName file. It contains the mount parameters for the user directories.

Figure 1. Example of a generic entry in a MapName file, /etc/u/map
name               *
type               ZFS
filesystem         OMVS.&SYSNAME.<uc_name>
mode               rdwr
duration           nolimit
delay              10
setuid             no | yes
In the example, &SYSNAME. represents the system name while <uc_name> specifies that the name being looked up is to be represented in uppercase. The automount facility creates a directory containing that name and uses it as a mount point for the file system to be mounted. You can use <uc_name> to replace any level qualifier. For example, if the name of the directory that is being looked up is USER1, the automount facility will resolve the name in the following ways:
OMVS. <uc_name> = OMVS.USER1
OMVS. <uc_name>.ZFS = OMVS.USER1.ZFS

For a complete list of supported keywords, see the automount command in z/OS UNIX System Services Command Reference.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014