Using the automount policy

The default delay time for automount is 10. Do not use a value less than 10. To verify the setting of the delay time, use the USS_AUTOMOUNT_DELAY check provided by IBM® Health Checker for z/OS®.

Rule: You must keep the automount policy consistent across all the participating systems in the sysplex. The automount facility will not manage any directory until it can process the entire policy without encountering any errors.

Your automount policy most likely resided in the /etc/auto.master and /etc/u.map files. For those using shared file systems, each participating system has a separate /etc file system. In order for the automount policy to be consistent across participating systems, the same copy of the automount policy must exist in every system's /etc/auto.master and /etc/u.map files.

AUTOMOUNT is the preferred method of managing the /u directory. You do not need a mount statement for /u in the BPXPRMxx parmlib member.

For example, both SY1 and SY2 have the following files:

/etc/auto.master
```
 /u     /etc/u.map
```

/etc/u.map

 name       *
 type       ZFS
 filesystem OMVS.<uc_name>.ZFS
 mode       rdwr
 duration   60
 delay      60

When the automount daemon initializes on SY1, it will read its local /etc/auto.master file to identify what directories to manage; in this case, it is /u. Next, the automount daemon will use the policy specified in the local /etc/u.map file to mount file systems with the specified naming convention under /u. The automount daemon on SY2 will perform similar actions. Because all mounted file systems are available to all participating systems in the sysplex, your automount policy must be consistent. This is true for the file system name specified in /etc/u.map and the values for other parameters in /etc/u.map and /etc/auto.master.