HP StorageWorks XP24000 for FlashCopy Mirroring Software User's Guide (T5240-96001, June 2007)

TrueCopy Synchronous for Mainframe pair is either Duplex of Pending duplex, the command
will be rejected and you cannot establish a Version 2 relationship.
Results of TrueCopy Synchronous for Mainframe operations
If a
Version 2 relationship is established with the FREEZE option and if a TrueCopy
Synchronous for Mainframe R-VOL is in the extended long busy (ELB) status, the command
to
create or resume a pair will be rejected. However, the command to suspend or delete
a
pair will b e executed normally.
When you use a Version 2 S-VOL as the TrueCopy for Mainframe R-VOL, c ongure the system
as
follows:
Connect different hosts to the main subsystem and remote subsystem, or connect the host of
the
main subsystem to both the main and remote subsystems.
Use the Fibre Channel interface to connect the main subsystem with the remote subsystem.
Note:
The above-mentioned system conguration differs from the system conguration that is used
when IBM FlashCopy Version 2 and PPRC are used in conjunction.
Unlike when IBM FlashCopy Version 2 and PPRC are used in conjunction, you need a DFSMS command
or a
TSO command when you use Version 2 and TrueCopy for Mainframe in conjunction. The procedures
when you use a DFSMS command or a TSO command are as follows. Note that the procedures differ
depending on whether Version 2 is used in conjunction with TrueCopy Synchronous for Mainframe or
TrueCopy Asynchronous for Mainframe.
Procedure when you use a DFSMS command
Follow the procedure below if you use a DFSMS command. However, if the status
of the TrueCopy Synchronous for Mainframe pair is duplex, you need to use a TSO
command. For details about the DFSMS to establish a Version 2 relationship, see
Establishing Version 2 Relationships by Volumes Using the DFSMSdss Command on page 77.
If the Version 2 S-VOL and TrueCopy Synchronous for Mainframe R-VOL are shared:
1. If you need to terminate the I/O operation to the volumes of the TrueCopy Synchronous
for Mainframe pairs in order to m a intain the consistency of data, terminate the I/O
operation.
2. Suspend the TrueCopy Synchronous for M ainframe pair. See the following example:
CSUSPE
ND DEVN(X dev#’) PRIM(X ssid’ cmd_param X cca X lss)
SEC(X ssid’ serial# X cca X lss)
3. Set the TrueCopy Synchronous for Mainframe R-VOL to online.
The hostwillbeabletorecognize thedataset on theTrueCopySynchronous for
Mainframe R-VOL and gure out the extent for establishing a Version 2 relationship.
Note:
If the same host is c onnected to both the TrueCopy Synchronous for Mainframe
M-VOLand R-VOL, theR-VOL labelmustberewritten.
4. Use DFSMS to establish a Version 2 relationship. S ee the following example:
COPY FULL INDYNAM(xxxxxx) OUTDYNAM(yyyyyy) FASTREP(REQ) FCCOPY
5. If step 4 completes successfully, set the TrueCopy Synchrono us for Mainframe R-VOL
to
ofine.
6. Resyn
chronize the TrueCopy Synchronous for M ainframe pair.
If the Version 2 S-VOL and TrueCopy Asynchronous for Mainframe R-VOL are shared:
1. If you need to terminate the I/O operation to the volumes of the TrueCopy Asynchronous
for Ma
inframe pairs in order to maintain the consistency of data, terminate the I/O
operation.
2. Suspend the TrueCopy Asynchronous for Mainframe pair. See the following example:
CSUSPEND DEVN(X dev#’) PRIM(X ssid’ cmd_param X cca X lss)
SEC(X ssid’ serial# X cca X lss)
3. Set the TrueCopy Asynchronous for Mainframe R-VOL to online.
The h
ost will be able to recognize the dataset on the TrueCopy Asynchronous for
Mai
nfra me R-VOL and gure out the extent for establishing a Version 2 relationship.
52
About
Version 2 Operations