The HISTFILE retains job statistics on a long-term basis. It is used for creating a history report. Since it will create new records for every new run of job, over time it grows very fast, so you must archive data from the history data sets to tape or disk. Running the HISTFILE archive job periodically (weekly or monthly) is recommended.
Note: From r11.3, you can generate application history reports in a similar way to which you generate job history reports.
Reason for critical impact
This job needs to turn off the tracking first, and turn on the tracking after completes. When the TRACKING is set to NOSTORE, tracking requests are accumulated in the checkpoint data set, which is very small and will be out of space quickly. And since tracking data cannot be processed, job status is not updated.
If the archive job runs too long or fails, you will notice:
OPER HISTFILE HIST1 OPEN OPER TRACKING STORE
Important! Since TRACKING is turned off, the failure of the archive job can NOT be reported automatically.
How to avoid
What to do if it occurs
It will take normally 5-30 minutes to resume the processing. If "LISTCKPT" issued from page mode shows no difference on "HIGHEST ADDRESS USED" and "BYTES IMBEDDED FREE SPACE", then COLD start will be needed to reformat the checkpoint file. Please review Chapter 3 in the Operator's Guide for the impact of starting CA Workload Automation EE system with parm=COLD.
Release: WKLASG00200-5.5-Workload Automation-Service Governor-EE
Please Update This Required Field