HP StorageWorks XP Remote Web Console Software - Manual (Page 186)

Table 55 Resolving TrueCopy for Mainframe Async Suspension Conditions
Recovery procedure SIM Causes of Suspension Classification
According to SIM, remove
the hardware blockade or
failure.
Re-establish failed pairs
(Resume Pair).
DB0x
DB1x
DB2x
Hardware redundancy has
been lost due to some
blockade condition. As a
result, MCU-RCU
communication, creating or
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.
MCU/RCU hardware
Remove the failed condition
at the RCU/MCU or on the
remote copy connection.
Re-establish failed pairs
(Resume Pair).
DB0x
DB1x
During the power-on-reset
sequence, the MCU could
not communicate with the
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.
MCU-RCU communication
Release failed pairs (Delete
Pair).
Reconsider the performance
resources necessary, and
increase resources as
needed (cache amount,
number of MCU-RCU paths,
etc.).
Re-establish failed pairs
(Add Pair).
DB1x The unrecoverable RIO
(remote I/O) timeout
occurred due to overload of
the RCU or the
communication facilities on
the remote copy
connections.
No recordset could be sent
within the specified copy
pending timeout.
The RCU could not settle the
pending recordset before the
copy pending timeout due
to overload of the RIO or the
RCU itself.
RIO overload
186 Troubleshooting