Previous Topic: TMSCTLG Report Field DefinitionsNext Topic: User Exit


TMSCYCLE Utility—Remove Tapes from Cycle Control

Use the TMSCYCLE utility to select all TMC records with an EXPDT subject to Cycle Control (CYCLE/ccc in control statements and online interfaces, or LABEL=EXPDT=99ccc in JCL), to determine if any volumes associated with the data set should be removed from Cycle Control.

TMSCYCLE retention is determined by the File 1 EXPDT only.

To remove volumes from Cycle Control, TMSCYCLE updates the expiration date in the TMC to the current date plus the number of days defined in the TMOOPTxx member of hlq.CTAPOPTN (RC parameter). TMSCYCLE does not consider the generation/version number for GDG data sets. Therefore, GDGs under Cycle Control may expire prior to meeting the GDG limit. If Cycle Control is used for ABARS pseudo GDG data sets (ending in ".CnnVnnnn"), system option ADGDG should be set to YES. This allows the pseudo GDGs to be treated the same way as regular GDG data sets. TMSCYCLE updates the X'04' bit in FLAG2 to indicate the volume has been expired from Cycle Control. Once expired, the volumes are eligible for scratch processing with the next execution of TMSCLEAN. Two other parameters in the TMOOPTxx member define the characteristics of a cycle to TMSCYCLE:

CA 1 considers all like tape data sets created during the same day to be one cycle if the system parameter option CDAY=DAY was specified in the TMOOPTxx member of hlq.CTAPOPTN. If the system parameter options CDAY=DAY and CJOB=JOB were specified in the TMOOPTxx member of hlq.CTAPOPTN, then different jobs creating the same data sets may be cycled differently and each tape data set may be considered a separate cycle. If you suspect that too many cycles are being held, verify the system options specified.

TMSCYCLE should be executed before TMSCLEAN to determine the scratch eligibility of tapes under Cycle Control.

CA 1 must be active or batch active to run this utility.