Activating and deactivating automatic job and started-task recovery

Automatic job recovery is normally started when HCL Workload Automation for Z is started. However, there are situations in which you might not want automatic job recovery, for example, when a recovery action might occupy resources required for other purposes.

You can inhibit automatic recovery in several ways. For example, you can specify this in the time parameter of the RECOVER statement and in the start-time and end-time parameters of the AROPTS (automatic job recovery options) statement. Another way is to deactivate automatic job recovery. When automatic job recovery is deactivated, ended-in-error jobs remain on the ended-in-error list, regardless of the presence of RECOVER statements.

When jobs that ended in error while automatic job recovery was deactivated are activated, they are first tested for RECOVER statements, and any necessary recovery actions are performed.

Note: On the HANDLING OPERATIONS ENDED IN ERROR panel in the MCP panel, you can request (with the ARC row command) automatic job recovery for jobs ending in error, even if you have deactivated automatic recovery. But you cannot activate automatic recovery here unless RECOVERY(YES) is specified on the OPCOPTS initialization statement.

For information on using automatic recovery, see Automatic recovery of jobs and started tasks and What you need for automatic recovery.