CopyExport Tape Management

Products

• CA 1 Flexible Storage
• CA 1 Tape Management - Copycat Utility
• CA 1 Tape Management - Add-On Options

Issue/Introduction

1. Beginning to use IBM TS7760T Copy Export for the first time. How is CA1 set up to manage the Copy Export tapes?

2. After issueing the CopyExport command (LI EXPORT,713942), how is the TMC updated with the tapes that the library has exported in order to be vaulted. Currently, the TMC still shows these tapes as SCRATCH and unused.

3. The dataset name is hard coded.

 

After making this mod, what is expected from CA1 after a copy export reclaim command?

 

Environment

Release :

Component : CA 1 Tape Management

Resolution

 

If this is for physical volumes that were used for EXPORT processing then the modification to the CBRUXEJC exit comes into play along with the CTSXLIST utility call to this exit.

First step is to have the physical container volumes defined to the TMC. They can be in SCRATCH status or DELETE status. Since they will never be mounted to satisfy a scratch request, it really doesn't matter if they are simply in SCRATCH status. TMSXTEND can be used to add the volumes to the TMC.

Second, the CTSUXEJC sample exit (which is linked as CBRUXEJC) needs to be modified at label MOVSDSN to un-comment out 3 lines of code. These three lines will pass a pseudo dataset name to the CTSQSTS module, and this pseudo dataset name will then be applied to the Container Volume in the TMC. The WCDSN field also needs to be update to contain this psuedo data set name that you want assigned to the container volume.

When the modified CBRUXEJC exit is driven by the CTSXLIST utility, the Container Volume will be assigned the dataset name passed by the exit. It will also have the create date/time and last-use date/time updated to the date time that the first virtual-volume was exported onto it. It will also be assigned the same vault-location/slot-number of the first virtual-volume (if any). Of course, with the pseudo-dataset name assigned a vault rule can also be used to assign it to a vault location (keep it at the vault until it is expired). The Contain Volume will also be assigned an expiration date of PERM and marked as an EDM volume.

Third, there is a sample EARL report called TMEACTVL that will then give a summary of all the virtual-volumes stacked on each container volume (sorted in expiration-date order of the virtual volumes I believe). If all the virtual-volumes on the container-volume are expired/scratched; the TMEACTVL will generate TMSUPDTE control statements to expire the Container Volume which will then signal the vaulting system to return it from the remote location.

If the TMEACTVL report shows a Contain Volume only have 1 or 2 active virtual-volumes on it; you might want to re-export those virtual-volumes (since the virtual-volumes still reside inside the VTS box). That would cause their ACTVOL to be updated to the new Container Volume and the old one would then be identified as not having any active Virtual-Volumes still on it; and it would be processed with the TMSUPDTE control statements and returned.

Hope this helps explain how the EXPORT processing works. Again, it gets more complicated than a MOVE/EXPORT with the addition of the CTSXLIST.