Many of the following utilities and reports are involved in the CA 1 daily maintenance cycle.
Note: For more information on these utilities, see the Utilities and Reports Reference Guide.
TMSEXPDT enables you to enforce tape data set retention standards. This utility updates the expiration date in the Tape Management Catalog (TMC) based on control statements in the Retention Data Set (RDS). Because TMSEXPDT is used to establish expiration dates in the TMC, TMSEXPDT must be executed before TMSCTLG, TMSCYCLE, and TMSCLEAN. The TMSCTLG and TMSCYCLE utilities use the expiration dates in the TMC to determine which data sets should be removed from Catalog Control and Cycle Control and expired. Expired data sets are eligible for scratch processing with the next execution of TMSCLEAN.
If TMSCTLG is needed, then as an option, the system utilities IDCAMS or IEHLIST can be executed to create a temporary data set for use by CTSLSTEX prior to TMSCTLG. Normally, TMSCTLG issues LOCATEs to the system catalog. The use of IDCAMS or IEHLIST eliminates the LOCATEs required, which reduces the runtime of the TMSCTLG program. An IDCAMS/IEHLIST input listing is required if nonshared system catalogs exist in an environment where multiple CPUs share the TMC.
If you are using CA 1 Catalog Control (CATLG or CATALOG in control statements and online interfaces, or LABEL=EXPDT=99000 or ACCODE=xCACATLG in JCL) for your tape data sets, and the TMOOPTxx parameter OCTLG is set or defaulted to YES, then TMSCTLG should be executed after TMSEXPDT and before TMSCLEAN to identify those data sets which no longer have an entry in the system catalog. TMSCTLG determines which data sets should be removed from Catalog Control. The expiration date in the TMC Volume record is changed to the current date plus an extension defined by parameter R9 in the TMOOPTxx member of hlq.CTAPOPTN, or the highest date from any secondary files. If the expiration date was changed to the current date, the next execution of TMSCLEAN places these tapes in scratch status.
If you are using CA 1 Cycle Control (CYCLE/ccc in control statements and online interfaces or LABEL=EXPDT=99ccc in JCL), TMSCYCLE should be executed after TMSEXPDT and before TMSCLEAN to identify those data sets which should be removed from Cycle Control. To determine if the tape should be expired, TMSCYCLE looks at the first file on the tape only. The expiration date in the TMC volume record is changed to the current date plus an extension defined by parameter RC in the TMOOPTxx member of hlq.CTAPOPTN. If the expiration date was changed to the current date, the next execution of TMSCLEAN places these tapes in scratch status.
TMSCLEAN is the primary method provided by CA 1 in which tapes under CA 1 control can be scratched and made available for output use. A tape cannot be reused until it is put into scratch status. This program determines which data sets should be removed from CA 1 Days Since Last Used Control (LDATE/ddd in control statements and online Interfaces or LABEL=EXPDT=98ddd in JCL). This program resets data sets using CA 1 Catalog Days Control (CATLG/ddd in control statements and online interfaces, or LABEL=EXPDT=90ddd in JCL) to CA 1 Catalog Control after the minimum ddd days requirement has been satisfied. It can optionally expire tapes whose expiration date exceeds the assigned SMS Management Class maximum retention value. The expiration date in the Volume record is changed to the current date.
If the OCTLG option is set to NO (indicating all systems sharing the TMC are at r11.5 or higher and have had the TMSOSCAT utility run with the SYNC option), TMSCLEAN changes the expiration date of all files set to Catalog Control that are no longer cataloged. You can then stop running TMSCTLG.
TMSCOPY should be executed daily, or as frequently as site needs require (such as once per shift), to back up the TMC and Audit data sets to tape. It should always be executed after daily maintenance, and is often executed prior to daily maintenance as well. The execution of TMSCOPY just before daily maintenance gives you the opportunity to restore the TMC to this backup level if there is a problem with the maintenance run. Invalid update activity resulting from the maintenance run can be discarded when the TMC is restored to its pre-maintenance state. It is a good idea to run TMSCOPY prior to execution of the Vault Management System (VMS) so that an alternate copy of the TMC can be moved with your other data sets to an off-site vault. VMS must be equipped with the data set name of this alternate backup.
The Vault Management System (VMS) consists of three batch programs: TMSVMEDT, TMSVMVLT, and TMSVMUPD. CA Earl is used to print the reports. If you plan to incorporate these programs into your daily maintenance job stream, they should be executed after TMSCLEAN has performed scratch processing. If VMS is executed before TMSCLEAN, it is possible that tapes being returned from off-site are expired and eligible to be scratched, and appear on the Scratch and Clean Listing while still in transit. Running TMSCLEAN prior to VMS prevents you from looking for scratch tapes that are not yet back in the library. If the vault programs are not included in your daily maintenance cycle, execute them whenever you are ready to move tapes off-site.
TMSVMEDT should be executed only after all tapes to be vaulted have been created. Otherwise, movement may not be complete, especially when a multivolume data set is still in creation. When TMSVMEDT selects the TMC records, only those volumes that have already been created and the volume still on the drive are considered. Volumes created subsequently are not moved until the next VMS execution.
Inventory, pre-staging, Audit, and customized reports are typically included in daily maintenance. Some of the more commonly used reporting programs and CA Earl source members are:
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |