BPXF243E F OMVS,NEWROOT COMMAND HAS BEEN TERMINATED DUE TO THE FOLLOWING REASON(S): text
Explanation
The request to switch the sysplex root file system has been terminated. One or more of the system environment conditions for changing the sysplex root file system needs to be corrected before continuing the sysplex root replacement.
The text can be one or more of the following:
- CURRENT SYSPLEX ROOT FILE SYSTEM IS UNAVAILABLE
- Indicates that the current root file system is not available. To replace an unowned current sysplex root file system, use the COND=FORCE option.
- NO FILE SYSTEM IS MOUNTED ON THE SYSPLEX ROOT
- Indicates that no file system is mounted on the current sysplex root.
- CURRENT SYSPLEX ROOT FILE SYSTEM IS QUIESCED
- Indicates that the current sysplex root file system is quiesced or super-quiesced by other activities.
- CURRENT SYSPLEX ROOT FILE SYSTEM IS MOUNTED RDWR
- Indicates that the current root file system is mounted in read/write mode.
- CURRENT SYSPLEX ROOT FILE TYPE IS INVALID
- Indicates that the current sysplex root file system PFS type is not HFS or zFS.
- CURRENT SYSPLEX ROOT HAS FUNCTION SHIPPING CLIENTS
- Indicates that a current sysplex root file system contains function shipping clients.
- CURRENT SYSPLEX ROOT IS EXPORTED
- Indicates that the current sysplex root file system directories are exported by programs. Two possible programs are DFS and SMB servers.
- NEW SYSPLEX ROOT FILE SYSTEM DATASET IS NOT FOUND
- Indicates that the new data set in the sysplex root file system specified cannot be found.
- NEW SYSPLEX ROOT FILE SYSTEM IS DFHSM MIGRATED
- Indicates that the new sysplex root file system is migrated.
- NEW SYSPLEX ROOT FILE TYPE IS INVALID
- Indicates that the new sysplex root file system type is neither HFS nor zFS.
- NEW SYSPLEX ROOT UID, GID OR MODE IS INVALID
- Indicates that new sysplex root UID, GID, or permission bits do not match the current sysplex root UID, GID, or permission bits.
- BYTE RANGE LOCKS ARE HELD IN CURRENT SYSPLEX ROOT
- Indicates that byte range locks are held in the current sysplex root file system.
- SYSTEM IS NOT CONFIGURED AS SHARED FILE SYSTEM
- Indicates that this system is not in the shared file system (sysplex) configuration.
- ONE OR MORE SYSTEM IS NOT AT THE REQUIRED LFS VERSION
- Indicates that at least one or more system is below the minimum LFS version level required for the NEWROOT command support.
- NEW SYSPLEX ROOT FILE SYSTEM IS CURRENTLY MOUNTED
- Indicates that the new sysplex root file system is currently mounted.
- NEW SYSPLEX ROOT FILE SYSTEM MOUNT FAILED
- RETURN CODE = retcode REASON CODE = rsncode
- Indicates that the new sysplex root file system mount failed on at least one system in the shared file system configuration.
- NEW SYSPLEX ROOT FILE SYSTEM DOES NOT CONTAIN THE FOLLOWING MOUNT POINT
- NAME: pathname
- RETURN CODE = retcode REASON CODE = rsncode
- Indicates that the new sysplex root file system does not contain all the mount points required. The new sysplex root file system at minimum must contain all the mount points defined on the current sysplex root file system.
- ANOTHER INSTANCE OF THE COMMAND IS ALREADY RUNNING
- Indicates that the F OMVS,NEWROOT command was already issued by another system on the shared file system configuration and is being processed.
- SYSPLEX ROOT FILE SYSTEM PFS TERMINATED
- Indicates that the current sysplex root file system PFS or new sysplex root file system PFS has terminated. The current sysplex root file system’s PFS or new sysplex root file system’s PFS has terminated. The current sysplex root file system’s PFS and the new sysplex root file system’s PFS must be up in all systems in the sysplex in order to continue the sysplex root migration processing.
- NEW SYSPLEX ROOT FILE SYSTEM DOES NOT CONTAIN THE FOLLOWING SYMLINK
- NAME: pathname
- RETURN CODE = retcode REASON CODE = rsncode
- Indicates that the new sysplex root file system does not contain the symlinks required. The new sysplex root file system at minimum must contain all the symlinks defined on the existing sysplex root file system.
- FOLLOWING SYMLINK CONTENT DOES NOT MATCH
- NAME: pathname
- Indicates that the symlink contents in the new sysplex root file system does not match the symlink contents in the existing sysplex root file system. The new sysplex root file system at minimum must contain all the symlinks defined on the existing sysplex root file system and the contents must be the same.
- F OMVS,NEWROOT COMMAND NOT COMPLETED ON ONE OR MORE SYSTEMS
- SYSTEM NAME: systemname
- Indicates that the new sysplex root file system update failed for some internal reason. At minimum the sysplex root filesystem in this system is in incomplete state.
System action
The sysplex root file system is not replaced. The processing stopped due to constraint violations.
Operator response
Contact your system administrator.
System programmer response
Verify that all the indicated requirements are met on all the systems in the shared file system configuration, and issue the request again.
For reason:
CURRENT SYSPLEX ROOT FILE SYSTEM IS UNAVAILABLE
Issue D OMVS,F
command to identify the cause. To replace an unowned current sysplex root file system, use the
COND=FORCE option.For reason:
CURRENT SYSPLEX ROOT HAS FUNCTION SHIPPING CLIENTS
Issue D
OMVS,F command on all systems to identify systems that do not have the sysplex root mounted
locally.For reason:
NEW SYSPLEX ROOT FILE SYSTEM IS DFHSM MIGRATED
HRECALL the data
set for the sysplex root file system.For reason:
NEW SYSPLEX ROOT UID, GID, or MODE is invalid
Temporarily mount
the desired new sysplex root and change the mode via the chmod shell command, or
change the UID or GID via the chown shell command as needed. The new sysplex root
must be unmounted before retrying the NEWROOT command.For reason:
NEW SYSPLEX ROOT FILE SYSTEM FAILED
Review the failing return
and reason code for the mount.For reason:
NEW SYSPLEX ROOT FILE SYSTEM PFS TERMINATED
Issue the D OMVS,P
command on each system to verify that the PFS is running. If the problem persists and the return and
reason codes suggest an internal error, search problem reporting databases for a fix for the
problem. If no fix exists, contact the IBM® Support Center.Module
BPXTXROT
Source
z/OS UNIX System Services kernel (BPX)
Routing Code
2
Descriptor Code
5,8