HP XP7 Continuous Access Synchronous for Mainframe Systems User Guide (TK911-96003)

DescriptionVolume
applies to
Split type
PPRCBCMRWC
Volume Write field. The S-VOL split type is, “by
Local Storage System”.
The user specified that the pair should be split. This
was done during the pair split operation from the
P-VOL
S-VOL
SUSPEND(04)SUSPOP(04)
SWAPPING(04)
Secondary
Volume by
Operator primary or secondary system by selecting Disable
for the Primary Volume Write field.
The secondary system received a request from the
primary system to split the pair. The P-VOL split
S-VOLSUSPEND(05)SUSPOP(05)by Local Storage
System
type is Suspended-Primary Volume by Operator or
Suspended-Secondary Volume by Operator.
The primary system detected an error condition at
the secondary system (RCU), that caused the
P-VOLSUSPEND(06)SUSPCU(06)by Remote
Storage System
primary system to split the pair. The S-VOL split
type is S-VOL Failure.
The primary system detected that the S-VOL status
changed to Simplex because the user released the
P-VOLSUSPEND(07)SUSPER(07)Delete pair to
RCU
pair from the secondary system. The pair cannot
be resynchronized because the S-VOL does not
have the Suspend status.
The primary system detected an error during
communication with the secondary system, or an
P-VOLSUSPEND(08)SUSPCU(08)S-VOL failure
error during update copy. In this case, the S-VOL
split type is usually S-VOL Failure. This split type is
also used when the number of paths falls below
the minimum number of paths setting on the Add
Remote Connection window.
The primary system could not find valid control
information in its nonvolatile memory during IMPL.
P-VOL
S-VOL
SUSPEND(09)SUSPER(09)MCU IMPL
This condition occurs only if the primary system is
without power for more than 48 hours (that is,
power failure and fully discharged backup
batteries).
The pair was split by the CGROUP/FREEZE TSO
command.
P-VOL
S-VOL
SUSPEND(0A)SUSPOP(0A)by FREEZE
The pair was split before the initial copy operation
was complete. The data on the S-VOL is not
identical to the data on the P-VOL.
P-VOL
S-VOL
SUSPEND(08)SUSPER(50)Initial copy failed
System behavior
Note the following behaviors for split pairs:
• The primary system stops performing update operations to the S-VOL. It may or may not
continue accepting write I/Os to the P-VOL depending on the P-VOL fence level setting and
split option.
• If an update fails, the primary system reports a unit check and notifies the host that Write fails.
This ensures that both the host system and application program regard the write operation to
the P-VOL as failed.
• If the primary system accepts subsequent write I/Os for a split P-VOL, the system records the
updated data in the P-VOL tracks as differential data. When a split pair is resynchronized,
the primary system copies the out of sync P-VOL tracks to the S-VOL as differential data.
Monitoring pair status, license capacity 79