Hitachi TrueCopy for IBM z/OS User and Reference Guide (T5211-96001, June 2007)

Performing TrueCopy for z/OS Configuration Operations 5-63
Hitachi Universal Storage Platform V TrueCopy for IBM z/OS User’s Guide
Changing from 3990 to 2105 or 2107 Emulation
TrueCopy for z/OS supports 3990-6, 3990-6E, 2105, and 2107 controller
emulation types for the USP V MCU and RCU. The 3990-6, 3990-6E, 2105 or
2107emulation is required for SMS I/O time-stamping of TCzA recordsets. The
2105 and 2107 emulation type is required for Compatible PAV operations.
Changing from 3990 to 2105 or 2107:
If you need to change the
emulation from 3990 to 2105 or 2107 for a USP V which has existing
Concurrent Copy (CC) pairs, you must:
1. Stop all Concurrent Copy jobs.
2. Change the CU emulation type of all CHA packages in the USP V to 2105 or
2107. For CC operations, 3990 and 2105 or 2107 emulations cannot be
intermixed in the same storage system.
3. Restart Concurrent Copy jobs.
Note: The PPRC commands are different for 3990 and 2105 or 2107 emulation
types.
Note on 2105 or 2107 CU Emulation Type of MCU: When the CU
emulation type of MCU is 2105 or 2107, and a host system is online to R-VOL,
even if you want to create a TC-MF pair by using the CESTPAIR command,
the CESTPAIR command is rejected. If you use the ONLINSEC(YES), you
can create a TC-MF pair even though a host system is online to R-VOL. If you
do not use the ONLINSEC (default), or if you use the ONLINSEC(NO), you
cannot create a TC-MF pair. If RCU does not support the 2105 or 2107 CU
emulation type, you cannot check whether a host system is online or not. In
this case, if you use the CESTPAIR command, and both MCU and RCU fulfill
the following condition, specify the ONLINSEC(YES).
• MCU is USP V, and the host on the MCU side is connected to the package of
2105 or 2107 CU emulation type.