For best results, and to ensure that stacked volumes are moved to the location determined by DFSMSrmm inventory management vital record processing, ensure that EDGHSKP has been run with the VRSEL option before starting export processing. As logical volumes are exported, DFSMSrmm tracks the "in container" stacked volume and drives the stacked volume movement based on the required location of the contained logical volumes.

DFSMSrmm export processing support is based on the following process steps, which are recommended:

1. Define vital record specifications that specify locations to which data sets in the VTS should be moved. Use the vital record specification location name as the key for managing export. You could associate location names with different types of retention to have more control over the volumes that you want to export. The intention is that all the volumes with the same required location name, in the same export request, get exported together. In step 3, you will use the required location to help build the export list, but you can use your own selection of 'location names' in the export list.
2. Run DFSMSrmm inventory management vital record processing to determine which logical volumes should be moved and to set the required location for each volume to be moved.
3. Create a list of volumes to export after you run vital record processing. The required moves are volume moves that are identified during vital record processing or by changes made when you issue the RMM CHANGEVOLUME subcommand. Use the RMM SEARCHVOLUME subcommand with the REQUIRED and CLIST operands for each storage location to obtain volume information for the list as shown in Figure 1. DFSMSrmm returns a list of volumes to export that you can use as input for creating the export list logical volume file 1. Consider using the RETDATE operand to group the volumes that are expiring in the same time period into the same export request. You can direct the CLIST created from the SEARCHVOLUME using the RMMCLIST DD name to a data set allocated in the format required by EXPORT processing. Otherwise the volume list must be reformatted; the EDGJIMPC sample JCL provides an example of how to do this.
   In this example, the target storage location is 'STORE1'. This is specified for the REQUIRED operand. Substitute your VTS library name for 'vts' in the LOCATION operand. The CLIST operand causes a CLIST record to be written for each logical volume that matches the search; the record contains 'volser STORE1'. You can specify any value instead of STORE1, the library uses this value to group volumes on to stacked volumes by destination.

   Figure 1. Searching the required location for logical volumes

   RMM SEARCHVOLUME VOLUME(*) OWNER(*) LIMIT(*) REQUIRED(STORE1) LOCATION(vts) -
      CLIST('',' STORE1') RETDATE(2001/020)

   See z/OS DFSMSrmm Managing and Using Removable Media for information about the RMM SEARCHVOLUME subcommand. See these examples in SYS1.SAMPLIB for the format and required files for the export list volume:

   • CBRSPSXP is the sample JCL for export list volume scratch request.
   • CBRSPPXP is the sample JCL for export list volume private request.

   When stacked volume support is enabled, you can no longer track the movement of logical volumes using the LOCATION and DESTINATION fields of the volume information. Any volume exported on a stacked volume resides in a container and has no assigned location name. DFSMSrmm continues to manage the volume movement using vital record specifications for data sets and logical volumes, but uses this information only to set the REQUIRED location. DFSMSrmm never assigns a destination to a logical volume.

4. Start the export process as described in the z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries using the LIBRARY EXPORT command, the EDGSPLCS utility, or the CBRSPLCS sample program.

   The VTS export process runs asynchronously to DFSMSrmm processing. Once the export request has been initiated, VTS library signals trigger DFSMSrmm actions related to export processing.

   During the VTS export process, logical volumes are copied to a stacked volume and the stacked volume is completed. For each logical volume copied to the stacked volume, DFSMSrmm is notified of both the logical volume and stacked volume. DFSMSrmm updates the DFSMSrmm control data set with the volume serial number of the stacked volume as the 'in container'.

   During export processing, DFSMSrmm updates the 'In container' value for each logical volume exported. DFSMSrmm updates the stacked volume and tracks export completion, marking the stacked volume closed.

   As export completes, DFSMSrmm uses the required location of the stacked volume to attempt to start its movement. If the required location is not shelf-managed, DFSMSrmm sets the destination, but does not yet mark the stacked volume as being 'intransit'.
5. On completion of export processing, use the export status list file to verify that all the logical volumes are processed successfully.
6. You are now ready to manage the movement of the exported stacked volumes. The inventory management functions required depend on whether your storage locations are bin managed. If all the target storage locations are not bin managed, the stacked volumes already have their destination set. You can create a report extract and continue with the next step. If any of the target storage locations are shelf managed:
   • Set the destinations for the volumes by running inventory management storage location management processing.
   • Create a report extract.
   The above function can be a single run of DFSMSrmm inventory management.
7. Create movement report and pick lists by using the DFSMSrmm EDGRPTD report utility.
8. Use the movement reports to eject the stacked volumes from the VTS using the library manager and move them to the destination storage location. Transfer the stacked volumes in the export hold category to the exit station using the library manager console. Physically move the stacked volumes listed in your movement report from the VTS exit station to the destination storage location.
9. 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.
   Figure 2. Confirming volume moves for exported volumes

   RMM CHANGEVOLUME * CONFIRMMOVE(vts,ALL)

   The next run of inventory management processes the global confirmation of movement and updates all the stacked volumes that you have moved to reflect the completion of movement. If you want to update the stacked volume movement status in the CDS, run inventory management now.