CA-1 Modernization Guide

CA-1 tracks tape datasets and the physical tapes they reside on. It prevents accidental overwrites of tapes containing valid data by enforcing retention policies. CA-1 also automates tape library management tasks, such as offsite tape rotation.

CA-1 uses control statements entered via JCL (Job Control Language) to perform operations. For example, TMSCLEAN is used to mark tapes as scratch, and TMSCOPY is used to copy the CA-1 database.

CA-1 uses a database (typically VSAM) to store information about tapes, datasets, and their relationships. Reports are generated using batch jobs that access this database.

CA-1 can be integrated with other z/OS security products like RACF, ACF2, or Top Secret to control access to tape datasets and CA-1 functions.

Common commands include TMSCLEAN (mark tapes as scratch), TMSCOPY (copy the CA-1 database), and TMSAUDIT (audit the CA-1 database). These are typically executed via JCL.

Basic operations are performed using JCL. For example, to mark a tape as scratch, you would submit a JCL job containing the TMSCLEAN command with the appropriate tape volume serial number.

CA-1 uses a VSAM database to store its metadata. The primary configuration is managed through JCL parameters and control cards.

CA-1 does not expose standard APIs like REST or SOAP. Integration is typically achieved through direct database access or by submitting JCL jobs.

CA-1 helps reduce the risk of data loss by preventing accidental overwrites. It also automates tape management tasks, which can save time and resources.

By automating tape rotation and offsite storage, CA-1 helps organizations meet compliance requirements related to data retention and disaster recovery.

CA-1 provides reports that can be used to track tape usage, identify tapes that are nearing their retention period, and optimize tape storage.

CA-1 integrates with z/OS security systems such as RACF, ACF2, and Top Secret to control access to tape datasets and CA-1 functions.

CA-1 leverages the security features of the underlying z/OS operating system and the integrated security products. It does not provide its own encryption mechanisms.

Auditing is performed through the integrated z/OS security system (RACF, ACF2, Top Secret) and through CA-1's own reporting capabilities, which track tape usage and management activities.

CA-1 is administered through JCL jobs and control statements. There is no GUI. User management is handled by the integrated z/OS security system.

Monitoring is typically performed by reviewing CA-1 reports and by monitoring the execution of JCL jobs. Logging is handled by z/OS system logging facilities.

Configuration parameters are set through JCL control cards. These parameters control tape retention policies, scratch pool management, and other operational aspects.