Split pair problems

True Copy for Mainframe User Guide for VSP One Block 85

Version: 10.5.x
File Size: 2745 KB
Audience: anonymous
Part Number: MK-26VSP1B036-02
ft:lastEdition: 2026-06-23

The following table lists and describes split pair problems and provides corrective action to resolve the error.

Pair status/type	Applies to	Description	Corrective action
Suspend/P-VOL by Operator	P-VOL	The user split the pair from the primary system specifying Disable for the Primary Volume Write option. The S-VOL split type is by MCU.	Resynchronize the pair from the primary system.
Suspend/S-VOL by Operator	P-VOL, S-VOL	The user split the pair from the primary or secondary system specifying Disable for the Primary Volume Write option.	Resynchronize the pair from the primary system.
Suspend/by MCU	S-VOL	The secondary system received a request from the primary system to split the pair. The P-VOL split type is P-VOL by Operator or S-VOL by Operator.	Resynchronize the pair from the primary system.
Suspend/by RCU	P-VOL	The primary system detected an error condition at the secondary system, which caused the primary system to split the pair. The S-VOL split type is S-VOL Failure.	Clear the error condition at the secondary system or S-VOL, and then resynchronize the pair from the primary system. If you need to access the S-VOL to clear the error conditions, release the pair from the secondary system. After you clear the error conditions from S-VOL, re-create the pair.
Suspend/Delete Pair to RCU	P-VOL	The primary system detected that the S-VOL status changed to Simplex because the user released the pair from the secondary system. The pair cannot be resynchronized because the S-VOL does not have the Suspend status.	Release the pair from the primary system, and then re-create the pair. Delete the pair by using the raidcom add remote_copy_pair command without the -copy_mode none option. You can specify the -copy_mode none option only when the P-VOL or S-VOL data is unchanged.
Suspend/S-VOL Failure 0x08	P-VOL	The primary system detected an error during communication with the secondary system, or detected an I/O error during update copy. In this case, the split type for the S-VOL is usually S-VOL Failure.	Check the path status using the raidcom get rcu command. If errors occurred on the path, clear the error conditions. Clear any error conditions at the secondary system or S-VOL, and then resynchronize the pair from the primary system. If you need to access the S-VOL to clear the error conditions, release the pair from the secondary system. After you clear the error conditions, re-create the pair.
Suspend/MCU IMPL	P-VOL, S-VOL	The primary system could not find valid control information in its nonvolatile memory during the IMPL procedure. This error occurs only if the system is without power for more than 48 hours (for example, power failure or fully discharged batteries).	Resynchronize the pair from the primary system. An entire initial copy operation will be performed in response to the pair resynchronization request.
Suspend/Initial Copy Failed	P-VOL, S-VOL	The primary system split this pair during the initial copy operation due to invalid track format. The data on the S-VOL is not identical to the data on the P-VOL.	Release the pair from the primary system. Clear all error conditions on the primary system, P-VOL, secondary system, and S-VOL. Use ICKDSF to reformat the failed track. Perform initial copy again.
Suspend/by FREEZE	P-VOL, S-VOL	All TrueCopy for Mainframe pairs in the primary system are split by the CGROUP/FREEZE command.	Resynchronize the pairs from the primary system using the CESTPAIR (MODE=RESYNC) TSO command.