Recovering from errors on the JT archive log

About this task

If there is a write error on the JT archive log, follow this procedure:
  1. Check if any CP EXTEND or CP REPLAN job is running: if this is the case, cancel the job and submit it again after the Z controller has restarted and completed the initialization.
  2. Stop HCL Workload Automation for Z.
  3. Rename the data set to a temporary name.
  4. Allocate a new JT archive-log data set.
  5. Copy the old data set into the new data set. This can be done by IEBGENER or IDCAMS REPRO.
  6. Start HCL Workload Automation for Z.
If there is a read error on the JT archive log, follow this procedure:
  1. Stop HCL Workload Automation for Z.
  2. Delete the data set, and allocate a new JT archive-log data set.
  3. Start HCL Workload Automation for Z, and submit a daily plan job as soon as possible. Current plan recoverability is jeopardized while you are running an incomplete JT archive log.
Attention:
  • Do not start HCL Workload Automation for Z with the CURRPLAN(NEW) keyword specified on the JTOPTS statement until a new current plan is taken over by HCL Workload Automation for Z.
  • If a write error occurs on the JT archive log, you must follow the recovery procedure described in this section. Do not try to recover by running a CP REPLAN or CP EXTEND, because the system might hang, or by stopping and restarting the controller, because the tracking records might go lost or overwritten.