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

1
SAID values in “SAID Values for the LINK Parameters (=ports) of RMF PPRC Link-path Statistical Information (REAR CL2)” (page 48)
are different from the ones in “SAID Values for the PATH LINK Parameter (= ports) (REAR CL2)” (page 42) and “Typographic
Conventions for PPRC TSO Commands” (page 192) .
2
For the XP disk array, the name of the package location is 2L.
3
For the XP disk array, the name of the package location is 2L.
4
For the XP disk array, the name of the package location is 2K.
5 For the XP disk array, the name of the package location is 2F.
TPC-R Cooperation Support
When the Basic HyperSwap function of TPC-R that is an IBM software for the disaster recovery is
used, it must be used in the following conditions.
•
System option mode 114 is set to OFF.
•
System option mode 484 and 769 are set to ON.
•
TrueCopy for Mainframe synchronous pairs are created after the path from MCU to RCU and
the path from RCU to MCU are established.
When M-VOLs and R-VOLs are exchanged by using the Basic HyperSwap function, TrueCopy for
Mainframe synchronous pairs are resynchronized using the path that is already established.
Therefore, when the path is not established, the exchange using the Basic HyperSwap function
cannot be done.
From the point of view of performance, the recommended number of pairs under the Basic
HyperSwap function is up to 1,000 per CHA to which the path for accessing the TrueCopy for
Mainframe volumes is connected.
If the Basic HyperSwap function operation is performed from TPC-R, the MIH value of the host I/O
and host operation is about a second. Therefore, the MIH may be reported for the host I/O and
host operation.
Figure 8 Exchange of TrueCopy for Mainframe Synchronous Pairs M-VOLs and R-VOLs using TPC-R
Interoperability with Other Products and Functions
Some types of volumes used by non-TrueCopy for Mainframe and non-TrueCopy for Mainframe
Asynchronous functions can also be used as M-VOL and R-VOL of TrueCopy for Mainframe and
TrueCopy for Mainframe Asynchronous.
“Whether Non-TrueCopy for Mainframe and Non-TrueCopy
for Mainframe Asynchronous Volumes Can Be Used as TrueCopy for Mainframe and TrueCopy
for Mainframe Asynchronous Volumes” (page 50)
explains whether non-TrueCopy for Mainframe
Interoperability with Other Products and Functions 49