HP Hitachi TrueCopy for Mainframe User Guide (T5211-96014, November 2011)

Table 55 Resolving TrueCopy for Mainframe Async Suspension Conditions (continued)
Recovery procedureSIMCauses of SuspensionClassification
Re-establish failed pairs
(Resume Pair).
receiving recordset, or the
staging or de-staging
process could not complete.
The pending recordset
cannot be retained because
one side of cache storage or
shared memory has been
blocked due to hardware
failure.
MCU-Creating/sending
recordset failed due to
unrecoverable hardware
failure.
RCU-Reading/Settling
recordset failed due to
unrecoverable hardware
failure.
The drive parity group has
been in the correction-access
status while the TrueCopy for
Mainframe pair was in
pending state.
Remove the failed condition
at the RCU/MCU or on the
remote copy connection.
DB0x
DB1x
During the power-on-reset
sequence, the MCU could
not communicate with the
MCU-RCU communication
Re-establish failed pairs
(Resume Pair).
RCU within the specified
RCU ready timeout.
The RCU could not settle the
pending recordset or could
not communicate with the
MCU before the copy
pending timeout due to
MCU not-ready or
inoperative facilities on the
remote copy connections.
Release failed pairs (Delete
Pair).
DB1xThe unrecoverable RIO
(remote I/O) timeout
RIO overload
Reconsider the performance
resources necessary, and
occurred due to overload of
the RCU or the
communication facilities on
increase resources as
the remote copy
connections.
needed (cache amount,
number of MCU-RCU paths,
etc.).No recordset could be sent
within the specified copy
pending timeout.
Re-establish failed pairs
(Add Pair).
The RCU could not settle the
pending recordset before the
copy pending timeout due
to overload of the RIO or the
RCU itself.
According to SIM generated
at the RCU, remove the
failure.
DB2xThe RIO (remote I/O) could
not complete due to the
failure at the RCU.
RIO failure
General Troubleshooting 183