DFSMSrmm supports the importing of logical volumes that are defined to DFSMSrmm or not defined to DFSMSrmm. During entry processing for a logical volume, DFSMSrmm automatically adds the volume information to the DFSMSrmm control data set or leaves the volume to be processed on another system. DFSMSrmm does not automatically add rack numbers for logical volumes because rack numbers are not supported for logical volumes.

You can initiate the import of logical volumes independently of DFSMSrmm by using the library manager console and creating an import list volume.

1. Use the library manager console to transfer stacked volumes to be imported from the Unassign category to the Import category. See IBM System Storage TS3500 Tape Library Introduction and Planning Guide and IBM System Storage TS3500 Tape Library Operator Guide for more information about the library manager.
2. Create an import list volume. See these examples in SYS1.SAMPLIB for the format and required files for the import list volume.
   • CBRSPSIM -- sample JCL for import list volume scratch request.
   • CBRSPPIM -- sample JCL for import list volume private request.

   To create the volume list for file 1 of the import list logical volume, you can search in the DFSMSrmm control data set, tailor the DFSMSrmm report extract file tailoring, or use any other method to identify the volumes to be imported.

   You can use the RMM SEARCHVOLUME subcommand to build the list of logical volumes with their containing stacked volume and status as shown in Figure 1. Specify the TYPE(LOGICAL) operand and DFSMSrmm returns the container volume serial number, logical volume serial number, and volume status between your specified CLIST prefix and suffix strings. The resultant output file can be used as input for creating the import list logical volume file 1 after it is reformatted using the EDGJIMPC sample.

   Figure 1. Creating a volume import list

   RMM SEARCHVOLUME VOLUME(*) LIMIT(*) OWNER(*) DESTINATION(vts) -
      TYPE(LOGICAL) CLIST

3. Request import processing by using the CBRXLCS macro, the OAM CBRSPLCS sample programs, or the LIBRARY command.

   During import processing, the imported volumes can be automatically defined to DFSMSrmm or the volumes can be left for processing by another system if the library is partitioned. If the volume is already known to DFSMSrmm, the volume is accepted for processing if it is defined as an exported logical volume, otherwise the volume is rejected.

4. To complete the import, DFSMSrmm uses the cartridge entry processing installation exit to track logical volumes that are imported by the VTS. OAM calls the exit once for each logical volume imported. DFSMSrmm removes the stacked volume association for logical volumes. DFSMSrmm removes the 'in container' value for the logical volumes.
5. When all logical volumes on a stacked volume are imported, you must decide what to do with the stacked volume. For example, you can return the scratch volume to the pool of empty stacked volumes for use by the VTS; use the Library Manager console to transfer empty stacked volumes to other categories within the VTS so they are ready for reuse.