Recovering from errors on the job-tracking log
About this task
HCL Workload Automation for Z automatically recovers from read errors on a job-tracking log during restart. If the error occurs on the first record of the log, the NMM task regards the job-tracking log as empty. A read error on a record other than the first is treated as end-of-file.
When there are write errors on a job-tracking log, HCL Workload Automation for Z tries
recovery. If an inactive job-tracking log is available, HCL Workload Automation for Z switches
to that data set and continues processing. You can then shut down HCL Workload Automation for Z to
correct the problem with the data set. If HCL Workload Automation for Z is
unable to switch
to an inactive JT log, you need to:
- Stop HCL Workload Automation for Z.
- Reallocate the job-tracking-log data set.
- If a dual JT log is available, copy the data from the corresponding dual logging data set into the new JT log data set.
- Start HCL Workload Automation for Z.
If you are not using the dual-logging function, you will lose the job-tracking data, but your current plan should not be impacted. But there might be an impact if recovery is required at a later stage of the current plan. So extend or replan the current plan as soon as possible.