Automatically replacing the sysplex root file system with the alternate sysplex root file system if it becomes unowned

In a sysplex configuration, the alternate sysplex root file system is a hot standby for the sysplex root file system that is used to replace the current sysplex root file system when the sysplex root file system becomes unowned. The alternate sysplex root file system is established by using the ALTROOT statement in the BPXPRMxx parmlib member during OMVS initialization or by using the SET OMVS command.

Requirements: When replacing the sysplex root file system, take the following requirements into consideration:

A shared file system configuration is required. However, the sysplex can be a single system.
All systems in the shared file system environment must be at z/OS® V1R11 at the minimum.
The alternate sysplex root must have the same mount points and symbolic links as the current sysplex root. The mount points are validated during processing, but the symbolic links are not. If mount points are missing, the current sysplex root is not replaced by the alternate sysplex root.
The file system type for the alternate sysplex root and the current sysplex root must be either HFS or ZFS. They do not have to be identical.
The alternate sysplex root PFS must be active on all systems in the shared file system configuration.
If the SECLABEL class is active and the MLFSOBJ option is active, then the multilevel security label for the alternate sysplex root must be identical to the assumed multilevel security label of the current sysplex root.
The sysplex root or any directories in the sysplex root file system must not be exported by the DFS or SMB server.
The real path name for the mount points in the current sysplex root must not exceed 64 characters in length.

Restriction: The ALTROOT statement is ignored during processing of the F BPXOINIT,FILESYS=REINIT system command. You will have to manually issue SET OMVS=(xx) where BXPRMxx is the parmlib member containing the original ALTROOT statement.