z/VM: System Messages and Codes Š CP - z/VM - IBM

HCP2227E HCP2228I
COMMUNICATION FAILURE TO THE SECONDARY
DEVICE
A failure occurred in the PPRC communication
paths. The application-site storage control for
the primary device can no longer communicate
with the recovery-site storage control. The
PPRC pair has been suspended and no further
updates are made to the secondary device.
The application-site storage control continues
to update the primary device. It keeps track of
changed cylinders for re-synchronization with
the recovery-site subsystem after the problem
is corrected and the PPRC pair is
re-established.
CRITICAL VOLUME STATE
For an installation-selected critical volume, the
PPRC pair is set up so that all write operations
will fail following an unsuccessful update to the
secondary device. Such an unsuccessful
secondary-device update has occurred and the
PPRC pair has been suspended. No further
updates are made to either device.
INTERVENTION REQUIRED ON THE SECONDARY
The secondary device of a PPRC pair is in a
not-ready condition and the PPRC pair has
been suspended. The application-site storage
control continues to update the primary device.
It keeps track of changed cylinders for
re-synchronization with the recovery-site
subsystem after the problem is corrected and
the PPRC pair is re-established.
The variables in the message are as follows:
prdev srdev
The primary device number and the secondary
device number
aaaa The first four bytes of the storage control serial
number
bbbbb The last five bytes of the 12-byte sequence
number
cc Channel connection address of the device.
System Action: Unless CRIT(YES) has been
specified when the PPRC pair was established, the
processing continues in a suspended duplex state.
Based on the specific error reason, the primary volume
storage control continues to keep track of changed
cylinders, such that after the error is corrected, you may
select the RESYNC option to reestablish the PPRC pair.
However, depending on the nature of the error, if there
is a possibility that data has been lost on the secondary
subsystem or device, the recovery action requires a full
copy after the problem has been fixed and the PPRC
pair re-established.
Operator Response: The system issues this message
because of a hardware error. Follow the procedures for
your installations when reporting this error.
272 z/VM: System Messages and Codes — CP
Programmer Response: This is a hardware problem.
Collect the appropriate EREP information for diagnostic
output, and contact your hardware support personnel.
The full sense data is logged in the EREP user ID set
up on the system to which the error has been reported.
Note: Disaster and recovery protection is exposed until
this error is corrected and the PPRC pair is
re-established.
HCP2227E Device rdev is a volume of a PPRC
pair.
Explanation: The device specified on the DUPLEX
command was not duplexed because it is already a
volume of a PPRC pair.
System Action: System operation continues.
Operator Response: If an incorrect device number
was specified, enter the DUPLEX command again with
the correct device number.
HCP2228I DASD rdev THE SUBSYSTEM
TRACE DATA HAS BEEN SAVED -
{ss-XX-XX|ssid.p-cc-dd}
Explanation: Data was stored in the support facility as
the result of a trace event. The trace is normally set by
the service representative to fix intermittent problems.
The variables in this message are as follows:
rdev The device number.
ss-XX-XX
The physical identifier of the reporting storage
director.
ssid.p-cc-dd
The subsystem identifier, storage path number,
controller identifier, and device unit address of
the affected hardware components
This message is displayed in conjunction with other
messages that provide information about channel
command word, sense, user ID, and other variables
when necessary.
System Action: System operation continues.
Operator Response: Record the device and path
information, then contact your system support
personnel.
Programmer Response: Examine the EREP outboard
recorder (OBR) record for additional details as to the
cause of the failure. Refer to the hardware publications
for sense data format and descriptions. If a hardware
problem exists, contact your IBM Support Center
personnel to diagnose and correct the problem.