R0000 RECLAIM SUCCESSFUL FOR EXPORTED STACKED VOLUME  XXXXXX - YOU CAN RETURN IT TO THE SPECIFIED LIBRARY  LLLLLLLL This message is generated when the TS7700 successfully  completes reclaim processing for an exported stacked volume  ‘XXXXXX’  that was exported during a previous copy export  operation. Note:  A copy exported physical volume can become eligible for  reclaim based on the reclaim policies that are defined for its  secondary physical volume pool, or through the host console  request command. The exported physical volume  no longer contains active data  and can be returned to physical  tape library that is attached to  distributed library  ‘LLLLLLLL ’  from its offsite location for  reuse. If it is placed in  export-hold, it should be  returned when the next copy  export is completed. Message description Action needed 13.1.7 Copy Export and DFSMSrmm When a stacked volume that is associated with a Copy Export operation is ejected from a  library (placed in export-hold or is physically ejected from the library), you see status  message  E0006 , which is sent by the library (see Table 13-2 on page 747). Removable Media  Management (RMM) intercepts this message and performs one of the following actions: GLYPH<SM590000> If the stacked volume is predefined to RMM, RMM marks the volume as ejected or  in-transit and sets the movement/store date that is associated with the stacked volume.  GLYPH<SM590000> If the stacked volume is not predefined to RMM and the STACKEDVOLUME(YES) option  in RMM is specified, RMM automatically adds the stacked volume to its control data set  (CDS).  To have DFSMSrmm policy management manage the retention and movement for volumes  that are created by Copy Export processing, you must define one or more volume vital record  specifications (VRSs). For example, assume that all Copy Exports are targeted to a range of  volumes STE000 - STE999. You can define a VRS as shown in Example 13-1. Example 13-1 VRS definition RMM AS VOLUME(STE*) COUNT(99999) LOCATION(location) As a result, all matching stacked volumes that are set in AUTOMOVE have their destination  set to the required location, and your movement procedures can be used to move and track  them. In addition to the support listed, a copy-exported stacked volume can become eligible for  reclamation based on the reclaim policies that are defined for its secondary physical volume  pool or through the Host Console Request function (LIBRARY REQUEST). When it becomes  eligible for reclamation, the exported stacked volume no longer contains active data and can  be returned from its offsite location for reuse.  For users that use DFSMSrmm, when stacked volume support is enabled, DFSMSrmm  automatically handles and tracks the stacked volumes that are created by Copy Export.  However, which logical volume copies are on the stacked volume cannot be tracked. Retain  the updated export list file that you created and the library updated, so that you have a record  of the logical volumes that were exported, and which exported stacked volume they are  stored in. A copy exported stacked volume can become eligible for reclaim based on the reclaim  policies that are defined for its secondary physical volume pool or through the host console  request command ( LI REQ,libname,COPYEXP,volser,RECLAIM ).  750  IBM TS7700 Release 5.0 Guide