Install the OAM user exits CBRUXENT and CBRUXEJC using the instructions provided in the IBM Tape Library Support Manual. Source is provided in CAI.CTAPSAMP members CTSUXENT and CTSUXEJC that must be customized. Source is also provided for the optional Volume Not in Library exit in member CTSUXVNL.
Usermod TLMU003 may also be run to provide immediate scratch synchronization with the OAM TCDB. The SMP/E statements to apply TLMU003 are provided in member TLMJU003 of CAI.CTAPJCL.
As discussed above, CA TLMS logically allows retention and movement to be performed for virtual tapes but does not assign cabinet/slots to them. They are scratched when their retention schedule is exhausted. As TRS processes the retention schedule for a tape, it does NOT prevent movement because the tape is in an ATL or VTS. Instead, TRS creates a 'Move Report' entry which shows the tape moving from its location. The 'cabinet/slot' field is updated as follows:
For a physical (container) tape the TO location has a cabinet/slot assigned.
If you are vaulting data sets that are on virtual tapes and they go to different vaults, you will need to make some changes to CBRUXEJC and TLERPT21. In CBRUXEJC you will need to add logic to compare the DSN (and optionally other fields) and set different pseudo DSNs for the physical tapes to be created. TLERPT21 allows you to add the tape location to the EXPORT statement:
EXPORT,vvvvvv,L1 EXPORT,vvvvvv,L2
The vvvvvv is replaced with the VOLSER to be exported and L1 and L2 are examples of separate vaults you want physical volumes exported to. These names can be the vault name or any other meaningful destination for your site.
When CTSSYNC is run with these control statements, all tapes with L1 will be exported together, and all tapes with L2 will be exported onto another tape. This gives you the separation so that you can have exported tapes going to different vaults. If you are going to keep the physical tape offsite until it expires you do not need to add a vault pattern for the pseudo DSNs. If you need to keep them a number of days, then you need to have a new vault pattern with the pseudo DSN.
|
Copyright © 2014 CA.
All rights reserved.
|
|