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

IMPORTANT: Remote copy and disaster recovery procedures are inherently complex. Consult
your HP account team on sense-level settings and recovery procedures.
CSUSPEND/QUIESCE TSO Command
See IBM documents SG24-2595, SC35-0355, and SC35-0169 for important information on the
optional QUIESCE parameter for the CSUSPEND TSO command.
CAUTION: The QUIESCE option of the CSUSPEND command has been disabled by APAR
OW15247 or APAR OW15248. See either of these APARs and the latest IBM PPRC documentation
for detailed information on the QUIESCE option of the CSUSPEND command. Check with your HP
account team before using the CSUSPEND command with the QUIESCE option to suspend TrueCopy
for Mainframe pairs on XP storage systems. If the CSUSPEND command with the QUIESCE option
is issued to certain volumes (for example, active SPOOL, PAGE, or CATALOG datasets, active
SYSRES volume), the attached host(s) may enter a deadlock condition and may require a storage
control IML to correct the condition. TrueCopy for Mainframe Asynchronous does not support the
CSUSPEND/QUIESCE option.
IEA494I System Console Message
The IEA494I message is recommended as a trigger for automation over the IEA491E message,
because the IEA494I message is reported to all attached MVS hosts each time the M-VOL pair
status changes, whereas the IEA491E message is reported to only one host system.
Switching Operations to the Remote Site
If a disaster or failure occurs at the main site, the first disaster recovery activity is to switch your
operations to the remote backup site. The TrueCopy for Mainframe Synchronous R-VOLs are
recovered individually based on the pair status and M-VOL fence level information for each pair.
The TrueCopy for Mainframe Asynchronous R-VOLs are recovered based on pair status, consistency
status, and consistency time.
The basic procedures for switching operations to the remote backup site are:
1. Analyze the currency of the TrueCopy for Mainframe Synchronous R-VOLs and the consistency
of the TrueCopy for Mainframe Asynchronous R-VOLs.
2. Record the consistency time (C/T) of each group. The suspended TrueCopy for Mainframe
Asynchronous R-VOLs with consistency status of group will indicate the same C/T.
3. Perform file recovery as needed. The C/T of each TrueCopy for Mainframe Asynchronous
group can be used to retrieve lost updates.
4. At the remote site, suspend all pairs by issuing the CSUSPEND TSO command to the R-VOLs.
Use the TrueCopy for Mainframe Asynchronous group and drain suspend options to de-stage
pending updates in cache to the R-VOLs. And then, change the state of R-VOLs to simplex by
issuing the CRECOVER TSO command.
If PPRC is not installed, connect to each RCU, and release all TrueCopy for Mainframe pairs.
For TrueCopy for Mainframe Asynchronous pairs, select C/T for the Delete Range option on
the Delete Pair dialog box to release all consistent pairs in the group at the same time. This
option prevents you from accidentally using inconsistent pairs for disaster recovery. Release
all TrueCopy for Mainframe sync pairs in the MCU using the Deleting Mode-All option.
CAUTION: If necessary, use ICKDSF REFORMAT to change the labels (VOLSERs) of the
R-VOLs.
5. Make sure that all required file recovery procedures have been completed before varying the
R-VOLs online. If an IPL of the remote host system is not required, bring the R-VOLs online. If
an IPL is required:
172 TrueCopy for Mainframe Usage Scenarios