HP XP P9500 Storage - Manual (Page 75)

You should prepare for file and database recovery using files for file recovery (for example,
database log files that have been verified as current). You can also use the sense information with
system timestamp that is transferred via ERC.
CSUSPEND/QUIESCE TSO command
See the IBM documents SG24–2595, SC35–0355, and SC35–0169 for important information
on the optional QUIESCE parameter for the CSUSPEND TSO command.
The QUIESCE option of the CSUSPEND command has been disabled by APAR OW15247 or
APAR OW15248. Refer to either of these APARs and the latest IBM PPRC documentation for
detailed information on the QUIESCE option of the CSUSPEND command. Please check with your
HP account team before using the CSUSPEND command with the QUIESCE option to suspend
Continuous Access Synchronous Z pairs on P9500 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.
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.
Switch 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 site. R-VOLs are recovered individually based on the pair status and
M-VOL fence level information for each pair.
Procedure 22 To switch operations to the remote site
1. Record the pair status and fence level of each R-VOL.
2. Analyze the currency of the R-VOLs, based on its pair status and M-VOL fence level setting.
See
“Analyze R-VOL currency” (page 76) . For pairs with M-VOL fence level setting of Never,
further analysis is required. This can be done using sense information transferred via host
failover, or by comparing the contents of an R-VOLs with other files confirmed to be current
(for example, database log files). These R-VOLs should be recovered using files that you have
confirmed to be current.
3. Perform file recovery as needed.
4. Change the state of R-VOLs to simplex by issuing the CRECOVER TSO command.
5. If PPRC is not installed, connect to each RCU, and release all Continuous Access Synchronous
Z pairs. Release all Continuous Access Synchronous Z 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.
6. At the remote site, connect to each remote system and release all Continuous Access
Synchronous Z pairs.
When an R-VOL changes to simplex, you cannot distinguish it from a non-Continuous Access
Synchronous Z simplex volume. If necessary, use the volume manager to change the volume
labels of the R-VOLs.
7. Complete file recovery procedures.
8. When file recovery procedures have been completed, vary the R-VOLs online.
9. If an IPL of the remote host system is not required, bring the R-VOLs online. If an IPL is required:
Switch operations to the remote site 75