The FlashCopy® to URz Primary Volume function enables you to share Compatible FlashCopy® V2 T-VOLs and URz P-VOLs. When you share Compatible FlashCopy® V2 T-VOLs and URz P-VOLs, the status of the URz pairs must be Duplex, Pending, Suspend, or Suspending. You can create URz pairs after creating Compatible FlashCopy® V2 relationships. You can also create Compatible FlashCopy® V2 relationships after creating URz pairs but only when the specified options are used in the following host interfaces:
- DFSMSdss: FCTOPPRCPRIMARY
- TSO: TGTPPRIM (YES)
- ICKDSF: TGTOKASPPRCPRIM (YES)
- ANTRQST macro: TGTPPRIM (YES)
For information about using Compatible FlashCopy® V2 with URz, see Using Compatible FlashCopy® with Universal Replicator for Mainframe.
The requirements of the FlashCopy® to URz Primary Volume function are as follows:
- Universal Replicator for Mainframe is a prerequisite for using the FlashCopy® to URz Primary Volume function.
- The FlashCopy® to URz Primary Volume function can be used regardless of the status of URz.
- The FlashCopy® to URz Primary Volume function cannot be used for the URz configuration combined with the multiple primary system and secondary system using CCI.
- The FlashCopy® to URz Primary Volume function cannot be used for URz in 3DC multi-target configuration using 3 URz sites.
- Data that Compatible FlashCopy® V2 copies to URz P-VOLs is transferred asynchronously to URz S-VOLs. URz displays the progress of this asynchronous data transfer. Depending on the timing of the Compatible FlashCopy® V2 and URz copy operations, a time delay might occur between the Compatible FlashCopy® V2 copy operation and the URz copy operation, and the URz asynchronous data transfer might progress slowly.
- If the Compatible FlashCopy® V2 S-VOL and T-VOL are Dynamic Provisioning for Mainframe volumes, the number of pages remaining in T-VOL may differ depending on the timing.
- If you create URz pairs or resynchronize suspended pairs when Compatible FlashCopy® V2
relationships exist, Compatible FlashCopy® V2 prepares as many copies as the number of relationships. The larger the
number of relationships per volume, the longer it takes for URz pairs to
become Duplex. Even with less load, it takes approximately 1.5 times longer when the
URz
pairs are not used with Compatible FlashCopy®.
When using the Preserve Mirror FlashCopy® function, the maximum number of relationships (or datasets) per volume should be 2,000 or less. If that is not possible, you should create and operate one relationship for each volume. This causes non-data-set parts to be copied as well, but the status of the TCz pairs will change to Duplex in a shorter time.
- The volume copy operation (of which a T-VOL is a URz P-VOL) might not be performed by using some applications on the host. For details, see Why you use IBM Db2® Cloning Tool for z/OS®.
The copy process of Compatible FlashCopy® V2 relationships and URz pairs by the FlashCopy® to URz Primary Volume function is the same as that of the FlashCopy® to PPRC Primary Volume function.