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

Table 74 Differences of Copying Process Between IBM FlashCopy and Version 2 (continued)
Version 2 IBM FlashCopy Compared Item
When Version 2 pair in NOCOPY
mode is created using Universal
Replicator for Mainframe pair P-VOL,
the copy operation is executed on
Version 2 pair T-VOL and Universal
Replicator for Mainframe pair S-VOL.
Copy operation is not executed even if
Version 2 pair is deleted.
The value of BCE or BCP displays as
F(FALSE) though the value of #TRACKS
YET TO BE COPIED displayed by the
FLASHCPY QUERY RELATIONS
command of ICKDSF changes,
depending on the number of tracks for
which the copy has not been
completed.
Not supported Copying in NOCOPY mode in
FlashCopy to Universal Replicator for
Mainframe Primary Volume function
Failover command is received, but
after that, the Cersion 2 pair T-VOL will
be used as TrueCopy for Mainframe
R-VOL. Therefore, Failback command
is rejected.
Receives Failover/Failback command. Receiving Failover/Failback command
to TrueCopy for Mainframe pairs in
FlashCopy to PPRC Primary Volume
function
ReverseResync command is rejected
because Version 2 pair T-VOL will be
used as Universal Replicator for
Mainframe pair S-VOL.
Not supported Executing ReverseResync command
on Universal Replicator for Mainframe
pairs in FlashCopy to Universal
Replicator for Mainframe Primary
Volume function
Ends abnormally with CC=12. To avoid
abnormal ending, see
“If an ICKDSF
Command Ended Abnormally”
(page 154)
.
Ends normally. Execute ICKDSF command for Version
2 to TrueCopy for Mainframe pair
M-VOL in pending status.
Data can be copied from the Version
2 pair S-VOL to T-VOL but not to the
TrueCopy for Mainframe R-VOL. In this
state, if you release the Version 2 pair,
the data of TrueCopy for Mainframe
M-VOL and R-VOL will be different. Neither FlashCopy data nor PPRC
data can be copied. Establishing a TrueCopy for
Mainframe pair in NOCOPY mode
whose M-VOL is a Version 2 pair
T-VOL that you establish in NOCOPY
mode
Data can be copied from the Version
2 pair S-VOL to T-VOL but not to the
Universal Replicator for Mainframe
S-VOL. In this state if you release the
Version 2 pair, the data of Universal
Replicator for Mainframe P-VOL and
S-VOL will be different. Not supported Establishing a Universal Replicator for
Mainframe pair in NOCOPY mode
whose P-VOL is a Version 2 pair T-VOL
that you establish in NOCOPY mode
Comparison of Relationship Releasing Process
“Differences of Relationship Releasing Process Between IBM FlashCopy and Version 2” (page 151)
shows the relationship releasing process between IBM FlashCopy and HP Version 2.
150 Feature Comparison with the IBM Product