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

NOTE: Universal Replicator for Mainframe does not support operations in which one primary
data volume is copied to more than one secondary data volume, or more than one primary data
volume is copied to one secondary data volume.
Because Universal Replicator for Mainframe operates on volumes rather than on files, multivolume
files require special attention. For complete duplication and recovery of a multivolume file (for
example, a large database file which spans several volumes), make sure that all volumes of the
file are copied to the Universal Replicator for Mainframe secondary data volume, and use Universal
Replicator for Mainframe to ensure update sequence consistency across this group of secondary
data volume.
Duplicate VOLSER
When you select Entire as the initial copy option, the Universal Replicator for Mainframe initial
copy operation copies the VOLSER of the primary data volume to the secondary data volume, and
therefore the primary data volume and secondary data volume of the Universal Replicator for
Mainframe pair will have the same VOLSER. Since the host operating system does not allow
duplicate VOLSERs, the host system administrator must take precautions to prevent system problems
related to duplicate VOLSERs. For example, the Universal Replicator for Mainframe secondary
data volumes must be defined in the system generation so they do not come online automatically
(see the CAUTION below).
CAUTION: If the volumes which will become Universal Replicator for Mainframe secondary data
volumes are physically attached to the same system images as the production volumes which will
become the Universal Replicator for Mainframe primary data volumes, the following problems can
occur:
When a Universal Replicator for Mainframe pair is released, the old secondary data volume is
usually offline. When a host system is IPL'd (initial program loaded), the operator will be offered
both volumes and asked which volume should be left offline − the old duplicate volser message.
This can be confusing and is prone to error. To avoid duplication of VOLSER:
1. Identify the volumes that will not be accessed by the host system.
2. Perform CHP OFF or some other operation to ensure that the volumes are inaccessible.
3. When performing an IPL, you must perform LOAD CLEAR.
Volume Types
“Supported Emulation Types” (page 52) shows DKC and DKU emulation types that can be used
for the Universal Replicator for Mainframe software.
Table 11 Supported Emulation Types
Support type Emulation
All CU images that can be used with an XP disk array DKC
All mainframe volumes that can be used with an XP disk array DKU (Drive)
All DKC and DKU (drive) emulation types for XP disk arrays can be used for Universal Replicator
for Mainframe software. In Universal Replicator for Mainframe, the emulation types of the primary
and secondary data volumes are indicated.
The following CU emulation types can be used for MCUs (primary storage systems) and RCUs
(secondary storage systems): 3990-3, 3990-6, 3990-6E, 2105, 2107, A-65A2, H-65A2, A-65C1,
A-65C2.
The CU emulation type of an MCU can be different from the CU emulation type of the corresponding
RCU.
52 Preparing for Universal Replicator for Mainframe Operations