IBM ATL Recommendations and Procedures

Automated Tape Libraries and Virtual Tape Support › The IBM Tape Library › IBM ATL Recommendations and Procedures

IBM ATL Recommendations and Procedures

The following usermod found in hlq.CTAPJCL must be installed to provide support for the IBM ATL:

CTSJUCBX: Applies your customized source to CBRUXENT, CBRUXEJC (and optionally CBRUXVNL) to your z/OS linklib.

The following CA 1® Tape Management System Parameters and procedures should also be set:

ROBSCR=YES—set in the TMOOPTxx member of CTAPOPTN to enable real-time scratch processing.
WRKFLS=NO—set in the TMOOPTxx member of CTAPOPTN. This causes CA 1 to assign a one-day retention to all work files.
If YSVC=YES, update your security system to give OAM update access to the resource YSVCUNCD.

Run your normal daily CA 1 maintenance jobs. When TMSCLEAN runs, it notifies the ATL of the tapes that have been scratched. After your job for vault management, run TMEEJECT to build control statements for CTSSYNC to EJECT the cartridge from the ATL. As cartridges are returned from the vault, you can insert them back into the ATL.

Notes:

CA 1 must be active before other software products that use tape or look for the CA 1 mount messages. This includes, but is not limited to OAM for the IBM robotic devices.
CA 1 does not support scratch subpooling in the IBM OAM controlled ATL/VTS.
If you run the IBM ATL in a Peer-to-Peer configuration (with a second IBM ATL off-site mirroring your ATL on-site), the procedures are the same. Do not run the TMEEJECT job to create the eject list. In Peer-to-Peer configurations the elapsed run time of TMSCLEAN may be extended due to delays in communicating with the off-site ATL. If the elapsed time for TMSCLEAN becomes too long, you may optionally set SCRATCH to NO and run CTSSYNC with a parameter of SYNC to cause the status of recently scratched volsers to be synchronized with the TMC. This results in the scratch volumes being updated in the OAM TCDB to scratch status.