You can use PPRC TSO commands
in automated procedures to do certain
PPRC functions. The description in this topic, for example, outlines an automated
procedure to check PPRC volume status at system IPL time and resynchronize
volumes that are in suspended or duplex state.
Before you begin: You need
to be familiar
with the commands used in these steps. For more information, refer
to Peer-to-Peer Remote copy command descriptions.
Perform
the following steps to include PPRC TSO commands in automated
procedures:
- Put the CQUERY PPRC TSO command in either a
batch JCL job or PROCLIB
member to query the status of all primary volumes.
- Automatically
start the procedure at IPL time by putting the procedure
name into SYS1.PARMLIB(COMMNDxx). PPRC sends
the results from the query to the system's log.
- Use NetView®, or other
console automation product, to capture the output from the CQUERY
command and examine specific path and volume status information.
- Use NetView, or another
console automation product, to initiate jobs for any paths and volume
pairs that you need to reestablish. These jobs can be other procedures
and can use JCL substitution.
Note: - Consider attaching
a host to the secondary subsystem. If regular
production operations are going to take place at the secondary subsystem,
install an ECAM device there to monitor real space usage at that secondary
LSS. An ECAM device cannot be a secondary volume of a PPRC pair, however,
because the secondary device cannot receive I/O.
- Some storage
subsystems only send the SIM down the path that issues
the next SIO. Many subsystems, however, send the message down every
active path group. As a result, any host that is attached to the
subsystem can receive the ERP SIM messages. This is an important consideration
as you plan for disaster recovery.