To introduce logical volumes with data into a VTS library or to reintroduce logical volumes back into a VTS to reuse the volume serial numbers, the volumes must be imported into the library. An import can be performed at the host, with a list of logical volumes to import, or at the library manager, if a single logical volume is to be imported. For more information concerning importing a single logical volume, see Importing a single logical volume at the library manager.

With IMPORT LIST format 01, import option SCRATCH or INITIALIZE can be specified along with the volume serial numbers of the stacked and logical volume pairs. If this import option is omitted (blank), the data contents of the logical volume are copied into the VTS system and a data fragment file entry and the library manager record are created. If the option specified indicates “SCRATCH”, only the data fragment file entry and the library manager record are created (data contents not copied). If the option specified indicates “INITIALIZE”, only a library manager record for the volume is created. If a logical volume serial number is not included with the stacked volume serial number, the import option specified applies to all logical volumes on the stacked volume. If you are importing into a library that supports outboard policy management, any constructs that are associated with the volume at the time of the export are assigned to the volume on the import. IMPORT LIST format 02 can then be used to override these construct names.

With IMPORT LIST format 02, you can also specify additional options to initially set or override the policy management constructs that are associated with a volume. You can set these options on a global or a logical volume basis. Also on a global basis, the import list specification can indicate how the library manages policy names that have not been predefined (FAILIMPORT, CREATENAME, or USEDEFAULT).

File sequence two is written and later updated by the library manager to record the import status of each requested logical volume. All files must be written in the library specified format. see IBM TotalStorage Enterprise Automated Tape Library (3494) Operator’s Guide for details regarding the library specified format. See SAMPLIB member CBRSPSIM, SAMPLIB member CBRSPPIM, and SAMPLIB member CBRSPPIP for sample JCL that can be used to write the two required files on the import list volume.

The required stacked volumes containing logical volumes to be imported must be entered into the library before initiating the import operation at the library. If the import operation is initiated before the volumes have been entered and placed in the import category, the import operation immediately fails.

Once the import list volume is written and the stacked volumes are entered into the library, the host needs to notify the library of the logical volume being used for the import operation and to initiate the import operation at the library. The CBRXLCS external services programming interface FUNC=IMPORT or the LIBRARY IMPORT command can be used to initiate the import operation and to identify the import list volume. See Import logical volumes (IMPORT) and Importing logical volumes into a VTS for more information. Only one import operation can be queued or in progress at a time in a physical library. This is a different restriction than for export processing which allows one export operation at a time in each VTS system. Also, if an export operation is already queued or in process, an import operation initiated to the same VTS system as the export operation fails. However, an import operation initiated to a different VTS system is allowed.

When all of the requested logical volumes on a stacked volume have been imported, the library manager places the logical volumes in the insert category to be processed as part of normal cartridge entry processing. There are additional flags that are passed to the cartridge entry installation exit (CBRUXENT) to indicate that the volume is a logical volume and that it has been imported. The logical volume flag is also set for non-imported logical volumes entered into a VTS. This provides a mechanism for the tape management system to track logical volumes.

All attached hosts are notified once the import operation is complete. This enables the import completion status to be reported independently of the status of the host that initiated the import operation. If the attached host has the import list volume in its TCDB, messages are issued with the completion results of the import operation. See Import status messages for more information.

To release the import stacked volumes from the library, the operator can selectively eject the volume or volumes from the library at the library manager. Another operator option is to alter the volume from the import category to the insert category which would allow the stacked volume to be entered into a VTS or a non-VTS library for reuse as a scratch stacked volume or as a physical scratch volume. Before reusing an import stacked volume, make sure that all the logical volumes on the stacked volume either have been successfully imported, or that the data on the logical volumes is no longer needed.

If using DFSMSrmm as your tape management system, use the SEARCHVOLUME subcommand with CONTAINER(volser) to verify that no logical volumes are still associated with the stacked volume. This verification should indicate that all logical volumes have been imported. To reuse the volume as a scratch stacked volume, enter the volume into a VTS library. To reuse the stacked volume as a scratch physical volume, enter the volume into a non-VTS library. The new physical volume will be automatically added to the DFSMSrmm control data set if DFSMSrmm is used. For more information regarding DFSMSrmm commands, see z/OS DFSMSrmm Managing and Using Removable Media.