Copy export from the TS7740 Virtualization Engine (3957-V06 or 3957-V07)

A copy of the data within a TS7740 Virtualization Engine (3957-V06 or 3957-V07) can be removed from the library, both in a stand-alone and in a multi-grid configuration. Copy export enables a copy of the data to be used for disaster recovery purposes while the original data remains accessible for production use. For the recovery of the copy exported volumes, a modified disaster recovery process is used instead of an import. The copy export support creates a secondary copy of a logical volume in a secondary physical pool. The information in this section discusses the copy export capability provided by DFSMSrmm.

For information on copy export support, refer to z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries, the IBM Redbook, IBM System Storage Virtualization Engine TS7700: Tape Virtualization for System z Servers, and the following IBM Whitepapers: IBM Virtualization Engine TS7700 Series Bulk Volume Information Retrieval User's Guide and IBM Virtualization Engine TS7700 Series Copy Export User's Guide.

When a stacked volume associated with a copy export operation is ejected from a library (placed in export-hold or is physically ejected from the library) status message E0006 is issued by the library. RMM intercepts this message and:

If the stacked volume is not pre-defined to DFSMSrmm and stacked volume support is not enabled, no further processing is performed by DFSMSrmm.
If the stacked volume is not pre-defined to DFSMSrmm and stacked volume support is enabled, DFSMSrmm automatically adds the stacked volume to its CDS.
For pre-defined and newly-defined volumes DFSMSrmm sets the location and home location, the volume type, status, assigned date and time and marks it eligible for automatic movement.
When the E0006 message includes the 'IN EJECT' text the volume is marked intransit to indicate that the volume is being ejected and the volume movement date is set.

Then, during inventory management (which occurs only if stacked volume support is enabled), RMM invokes the CBRXLCS QVR interface to determine when an export-hold volume has been ejected.

The following E0006 messages are issued by the library and appear as part of the message text for message CBR3750I.

E0006 STACKED VOLUME xxxxxx FROM yyyyyy IN EXPORT-HOLD.
E0006 STACKED VOLUME xxxxxx FROM yyyyyy IN EJECT.

And will be displayed at the host as part of the message text for message CBR3750I:

CBR3750I Message from library library-name: message.

The results of volume processing for EXPORT-HOLD and EJECT are as follows:

When the volume is not yet defined to DFSMSrmm, and the STACKEDVOLUME(YES) control option is in use, the DFSMSrmm processing is as if the following command was used to add the stacked volume:

RMM AV volser TYPE(STACKED) STATUS(MASTER) MEDIATYPE(ETC) RECORDINGFORMAT(EFMT1) OWNER(EXPORT) 
    DESC('Created by Export') EXPDT(99365) HOME(lib) LOCATION(lib)

For copy export volumes (both pre-defined and newly defined volumes) in EXPORT-HOLD, the DFSMSrmm processing is as if the following command was used to add the stacked volume:

RMM CV volser TYPE(STACKED) STATUS(MASTER) LOCATION(lib) HOME(lib)
RMM CV volser AUTOMOVE CLOSE ASDATE(date) ASTIME(time)

For copy export volumes (both pre-defined and newly defined volumes) in EJECT the DFSMSrmm processing is as if the following command was used to add the stacked volume:

RMM CV volser TYPE(STACKED) STATUS(MASTER) LOCATION(lib) HOME(lib)
RMM CV volser EJECT AUTOMOVE CLOSE ASDATE(date) ASTIME(time)

To have DFSMSrmm policy management manage the retention and movement for volumes created by copy export processing, stacked volume support must be enabled. You must also define one or more volume VRSes. For example, assuming all copy exports are targeted to a range of volumes STE000-STE999 you could define a VRS;

RMM AS VOLUME(STE*) COUNT(99999) LOCATION(location)

When stacked volume support is enabled, and you want DFSMSrmm to manage the movement of copy exported stacked volumes you must run inventory management vital records and storage location management processing. (EDGHSKP with parameters including VRSEL and DSTORE). The required steps are:

Perform copy export either to EXPORT-HOLD or to EJECT
When all required copy exports are completed eject the stacked volumes in EXPORT-HOLD from the VTS using the library manager.
Note: If your TS7700 Virtualization Engine. is running microcode lower than Release 1.7 PGA4 (8.7.0.143) do not yet remove the ejected volumes from the I/O station. Otherwise, DFSMSrmm will not be able to determine the status of the volumes during inventory management correctly and will not set Intransit ON.
Run EDGHSKP with VRSEL and DSTORE. Optionally include a report extract to enable movement reports to be created.
Create movement report and pick lists by using the DFSMSrmm EDGRPTD report utility.
Physically move the stacked volumes listed in your movement report from the VTS exit station to the destination storage location.
Confirm that volumes have been moved. When the volumes have been moved, use the RMM CHANGEVOLUME subcommand, as shown in Figure 2 to confirm the completion of the movement of volumes.

A copy exported stacked volume can become eligible for reclaim based on the reclaim policies defined for its secondary physical volume pool or through the host console request command (LIBRARY REQUEST). When it becomes eligible for reclaim, the exported stacked volume no longer contains active data and can be returned from its offsite location for re-use. When the TS7700 Virtualization Engine has successfully completed reclaim processing for a previously exported stacked volume, the following message is issued by the library and also appears as part of the message text for CBR3750I:

CBR3750I Message from library library-name: R0000 RECLAIM SUCCESSFUL FOR EXPORTED STACKED VOLUME volser.

Note: This message is generated only for reclaims initiated by LIBRARY REQUEST. This message is not issued for reclaims of copy exported volumes that were made eligible through normal pool policy.

RMM intercepts this status message and, if a move is possible and required, marks the volume to be moved back to the library. The results of volume processing for a reclaimed volume are as if the following commands were issued:

RMM CV volser HOME(library-name)

Then, if the volume is not library resident, and is not currently moving, the following command:

RMM CV volser LOCATION(HOME)

Finally, the volume's required location is set to the library-name to ensure that if any further movement is needed, the correct destination can be set by inventory management DSTORE processing and the volume is placed under manual move control. The use of the MANUALMOVE setting ensures that the volume will not be moved again by existing VRS policies until reused for a later copy export.

Reclaim support is provided regardless of whether stacked volume support is enabled.