Automated Tape Libraries and Virtual Tape Support › IBM Virtual Tape Server (VTS) › IBM VTS - CBRUXEJC Volume Eject Exit

IBM VTS - CBRUXEJC Volume Eject Exit

The CBRUXEJC exit is invoked when a physical tape is ejected and when a virtual tape is exported. Modify this exit if you are using the VTS with the import and export functions. A pseudo DSN needs to be added to the code so that CA 1 can track the physical tapes used during the export. If you are using a VTS without the import/export feature, or if you are using an ATL, modification to the CA 1 supplied version is not necessary.

During an export function, the following actions are taken on the virtual volumes that are being exported:

• CA 1 clears the OUTCODE, OUTDATE, SLOT and ROBID fields
• ACTVOL is updated with the physical VOLSER that the virtual volumes are being exported to
• FLAG5 is set to 20 (VTX - Virtual Tape Exported)

The following actions are taken on the physical volume (also referred to as the container volume):

• The physical tape is taken out of scratch or delete status
• The EXPDT is set to PERM
• The DSN is set to the pseudo data set name that you have specified in exit CBRUXEJC
• FLAG3 is set to 20 (EDM - External Data Manager)
• Creation date (CDATE) is set to today's date
• The OUTCODE and SLOT in the physical tape are set to match the vaulting data from the first virtual volume that was exported to this physical volume
• OUTDATE is set to the current date

The pseudo DSN that is assigned to the physical volume should be added to the Vault Pattern Data Set to define the vault movement that is desired for exported VTS volumes. The vault system utility TMSVMEDT has been changed to skip all volume records that have the VTX (volume exported bit x'20') on in FLAG5.