DFSMSrmm support for import processing when stacked volume support is enabled

DFSMSrmm supports the importing of logical volumes that are defined to DFSMSrmm or not defined to DFSMSrmm. During import 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 as follows.

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.
Create an import list. See these examples in SYS1.SAMPLIB for the format and required files for the import list volume.
- CBRSPSIM is the sample JCL for import list volume scratch request.
- CBRSPPIM is the 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 data set, 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 these examples. When you specify the TYPE(LOGICAL) operand, DFSMSrmm returns the container volume serial number, logical volume serial number, and volume status between your specified CLIST prefix and suffix strings. Use the RMMCLIST DD to direct the CLIST output to a data set of the correct record format or use the EDGJIMPC sample to reformat it. You can then use the SEARCHVOLUME output file as input for creating the import list logical volume file 1.
When stacked volumes are returned to the library, you can build import lists by either using the logical volumes or using the stacked volumes. To build a list of stacked volumes to be imported, you can issue the DFSMSrmm TSO subcommand shown in Figure 1.
Figure 1. Building a list of stacked volumes to be imported from a single stacked volume
```
RMM SEARCHVOLUME VOLUME(*) OWNER(*) LIMIT(*) TYPE(STACKED) DESTINATION(vts) -
   CLIST
```
To build a list of logical volumes to import from a single stacked volume, you can issue the DFSMSrmm TSO subcommand shown in Figure 2.
Figure 2. Building a list of logical volumes to be imported from a single stacked volume
```
RMM SEARCHVOLUME CONTAINER(S12345) VOLUME(*) OWNER(*) LIMIT(*) TYPE(LOGICAL) CLIST
```
To build a list of logical volumes to import from multiple stacked volumes, you can issue the DFSMSrmm TSO subcommand shown in Figure 3.
Figure 3. Building a list of logical volumes to be imported from multiple stacked volumes
```
RMM SEARCHVOLUME VOLUME(*) LIMIT(*) OWNER(*) CONTAINER(*) -
   REQUIRED(vts) TYPE(LOGICAL) CLIST
```
Request import processing by using the EDGSPLCS utlity, 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.
To complete the import process, 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. For logical volumes, DFSMSrmm removes the stacked volume association. The stacked volume is updated to remove information for each imported volume.
When all logical volumes on a stacked volume are imported, the count of contained volumes is set to 0. You now 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.