Use the MODIFY OMVS command to dynamically replace the sysplex root file system. This support does not copy any directories, data, or links from one sysplex root to another, and active connections to any files or directories will be broken on replacement of new sysplex root file system.
Requirements or restrictions: The following
conditions are verified by the system before the replacement:
- Use this supported function only in the shared file system configuration. The sysplex can be a single-system sysplex.
- All systems in the shared file system environment must be at the level that supports this function.
- The current sysplex root PFS and the new sysplex root PFS are up in all the systems in shared file system configuration.
- The sysplex root must be locally mounted on all systems in the shared file system configuration.
- Byte range locks must not be held on the sysplex root during replacement processing.
- The current sysplex root and the new sysplex root must be either HFS or zFS in any combination.
- The sysplex root or any directories on it cannot have been exported by the DFS or SMB server.
- Remote NFS mounts of the sysplex root or any directories on it are considered as active use of the current sysplex root.
- During the replacement, the new zFS sysplex root file system must not be HSM-migrated, mounted, or in use.
- The UID, GID and the permission bits of the root directory in the new sysplex root file system must match those of the root directory in the current sysplex root file system.
- If the SECLABEL class is active and the MLFSOBJ option is active, the multilevel security label for the new sysplex root must be identical to the assumed multilevel security label of the current sysplex root.
|
The parameters are:
- NEWROOT=fsname
- Specifies the new sysplex root file system that is to replace
the existing one. The new file system must follow the sysplex root
file system convention described in z/OS UNIX System Services Planning. After the replacement, the MOUNT parameters are preserved or dropped depending on the type of the new file system:
- If the file system type is the same as the old file system, the MOUNT specifications are preserved.
- If the file system type is different from the old file system, the MOUNT specifications are dropped.
- If the MOUNT parameters have been dynamically changed, they are dropped anyway.
- COND=YES
- Proceed conditionally.
Failure message BPXF244E is displayed.
If any active usage is found in the current sysplex root file system,
report the active usage through BPXF245I message to the console and
stop the command processing. The default is COND=YES. - COND=NO
- Proceed unconditionally. If any active usage is found in the current sysplex root file system, report the active usage through BPXF245I message to the console and continue processing the command to replace the current sysplex root file system with the new sysplex root file system. Active connections to any files or directories in current sysplex root file system will be broken when the new sysplex root file system replaces the current one, and might get an EIO return code.
- COND=FORCE
- Use the FORCE option if the current sysplex root file system is
failing or unowned.The BPXI085D message is issued to the console to confirm the FORCE option. Mount points are validated. Symbolic links are not validated. In addition to the restrictions listed previously, the following restrictions must be met to use the FORCE option:
- All systems in the sysplex must be at the V1R11 level or higher.
- The mount points in the current sysplex root file system must not exceed 64 characters in length.
For more information about replacing the sysplex root file system, see z/OS UNIX System Services Planning.