The new architecture of the CMT and JEHF files utilizes Datacom/AD which eliminates the need to regularly schedule a maintenance window for compressing the CMT and for reorganizing the JEHF. In previous releases the maintenance process required that the CA 11 DBAS be shut down.
The MANT task, an automated function within the CA 11 DBAS started task, uses user defined criteria to perform maintenance. This maintenance was previously handled by batch utilities, U11UTI to purge the JEHF information to tape and U11D9015 to delete old CMT members. The MANT task now interfaces with Datacom/AD for the purpose of purging old records, purging unused jobs or purging both.
The MANT TASK is driven by several parameters in the CONFIG file. These parameters are as follows:
|Specifies the number of days used to compare against a CMT job's last accessed date to determine if a job should be deleted. The default is zero which means do not delete any jobs.
|Specifies the number of days between maintenance cycles. Values can range from 0 to 248. The default is 5.
|Specifies the number of concurrent DBAS request used to determine if DBAS is to busy to perform maintenance on another job element. The maximum number of initiators is recommended as a starting value. The default is 1000.
|This is the number of days used to compare against a TEMP JOB element's last accessed date to determine if TEMP JOB element should be deleted. The default is zero which means delete a TEMP JOB element immediately. To use this feature requires that user exit U11TMPEX be used to select with jobs are TEMP JOBs.
|Specifies the number of days used to compare against an audit record's creation date to determine whether to delete an audit record. The default is 30
The CA 11 Options Table values for history cleanup are also used.
|The maximum number of days that a history production record (and associated reruns) should be kept.
|The minimum number of history production records (and associated reruns) to keep for a job, even if MAXDAYS is exceeded.
Set the parameters and options accordingly for deleting information from the CMT and JEHF based on your site's requirements.
A record is purged from the CMT once the MAINTAGE value has been reached. This is the equivalent of DAYS=nnn for the U11D9015 program in the prior release which indicated the point at which a member would be deleted from the CMT.
A record is purged from the JEHF once the MAXDAY option and MINCNT option values are reached. SET2PURG flag may be set to YES in JEHF records whenever there is a desire to purge JEHF records that have not yet reached the MAXDAY and MINCNT values. Any JEHF record with this flag set to YES will be deleted during the next maintenance cycle. The JEHF also stores audit records if AUDITSUP=YES is specified in the config file. Audit records are purged by the MANT task once the AUDITAGE value has been reached.
The way this whole process starts is the MANT task automatically kicks off when DBAS is started. This task then wakes up when the MAINTTME value is reached. The MANT task only needs to run on one LPAR even if several LPARS share the CMT and JEHF. The MANT task should run where the Datacom/AD Multi-user Facility (MUF) resides. All other LPARS should have a MAINTTME value of 0.
To run the MANT task at will, set MAINTTME to 0 and issue "comchar START MANT" operator command. This allows the MANT task to attach and run immediately. Once completed the MANT task will detach.
Moving the CA 11 CMT and JEHF into Datacom/AD has enabled the end user to perform the maintenance process without having to schedule any type of outage, thus increasing system availability.
When MANT is completed, the index will have empty index records. It is recommended to run a DBUTLTY DEFRAG after the MANT process to clean up and recover all of the empty index record slots. A consequence of not running DEFRAG is that the IXX could fill up rather quickly. For more information about the IXX for CA11 reaching 80%+ and receiving message U11D-8200-5, please refer to Article ID: 33161
For more information about the DBUTLTY DEFRAG function, please see the CA Datacom/DB DBUTLTY Reference Guide.