Recovering from errors on the job-tracking log

IBM Tivoli Workload Scheduler for z/OS 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, IBM Tivoli Workload Scheduler for z/OS tries recovery. If an inactive job-tracking log is available, IBM Tivoli Workload Scheduler for z/OS switches to that data set and continues processing. You can then shut down IBM Tivoli Workload Scheduler for z/OS to correct the problem with the data set. If IBM Tivoli Workload Scheduler for z/OS is unable to switch to an inactive JT log, you need to:

1. Stop IBM Tivoli Workload Scheduler for z/OS.
2. Reallocate the job-tracking-log data set.
3. If a dual JT log is available, copy the data from the corresponding dual logging data set into the new JT log data set.
4. Start IBM Tivoli Workload Scheduler for z/OS.

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.