search cancel

Performing maintenance to CA Workload Automation Restart Option for z/OS Schedulers to clean up the CMT and JEHF

book

Article ID: 42136

calendar_today

Updated On:

Products

CA-11

Issue/Introduction

Summary: 

The new architecture of the CMT and JEHF files uses CA-Datacom/AD after release 3.0    The CA-11 MANT task  eliminates the need to regularly schedule a maintenance window for compressing the CMT and for reorganizing the JEHF, which in previous releases required that 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 CA-Datacom/AD for the purpose of purging old records, purging unused jobs or purging both.

 

This documents discusses how the MANT task works and the parameters and options used as criteria for determine what information is deleted from the CMT and JEHF when the MANT tasks runs. 

 

Instructions: 

The MANT task runs automatically if MAINTTME value in the config file is set to a non-zero value.  If the value is set to zero the task will have to be started manually by issuing the following DBAS command

COMCHAR START MANT     (where COMCHAR is the value defined in the config file)

A record is purged from the CMT once the MAINTAGE value has been reached.  Records are purged from the JEHF once both the MAXDAY and MINCNT option values are reached.   The JEHF also stores audit records if AUDITSUP=YES is specified in the config file.  Audit records are purged once the AUDITAGE value has been reached.

Set the parameters and options accordingly for deleting information from the CMT and JEHF based on your site’s requirements.

The MANT TASK is driven by several parameters in the CONFIG file. These parameters are as follows:

 

MAINTAGE:

Specifies the number of days used to compare against a CMT job's last accessed 0 date to determine if a job should be deleted. The default is zero which means do

Not delete any jobs.

MAINTTME:

Specifies the number of days between maintenance cycles. Values can range from 0 to 248. The default is 5.

MAINTRQS:

Specifies the number of concurrent DBAS request used to determine if DBAS is too busy to perform maintenance on another job element. The maximum number of initiators is recommended as a starting value. The default is 1000.

MAINTMP:

This is the number of days used to compare against a TEMP JOB element's last 0 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.

AUDITAGE:

Specifies the number of days used to compare against An audit record’s creation date to determine whether to delete and audit record.  The default is 30. 

MAINTTMP:

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.


The CA 11 Options Table values for history cleanup are also used.

MAXDAYS:

The maximum number of days that a history production record (and associated reruns) should be kept.

MINCNT:

The minimum number of history production records (and associated reruns) to keep for a job, even if MAXDAYS is exceeded.

 

For further information about the MANT task parameters please see the CA 11 Programmer Guide.  As always,  please contact Broadcom support for CA Workload Automation Restart Option for z/OS Schedulers if you have  further questions.  
 



Environment

Release: ELEVEN00200-11-Workload Automation-Restart Option-for Z/OS Schedulers
Component:

Resolution

Please Update This Required Field