Previous Topic: DSN Table Overflow WTO MessageNext Topic: CA Service Desk Interface

Changes to Existing Features › Interface with CA WA Restart Option

Interface with CA WA Restart Option

CA Workload Automation SE lets users define job or step level condition codes to determine whether a job completes successfully. The interface with CA WA Restart Option, formerly known as CA 11, has been enhanced to synchronize job success/failure criteria between the two products. This enhancement lets CA Workload Automation SE control restart processing for jobs under its control, as opposed to the operating system and CA WA Restart Option database. In other words, CA Workload Automation SE informs CA WA Restart Option of the restart step (ignoring the CA WA Restart Option HIRTCD), but CA WA Restart Option still determines the appropriate step in which to restart the job.

In addition, this enhancement lets CA Workload Automation SE tell CA WA Restart Option the JESNODE where the job ran and the CA WA Restart Option subsystem that controls the job, leading to greater accuracy for job restarts.

By default, this feature is disabled. Sites wanting to use this feature must set the RESTART file initialization statement keyword CONDCHK to YES. This keyword, new to release 11.3, is documented in the Systems Programming Guide.

The updated CPU Job in Restart Status panel (QM.4-X) includes two new display only fields, CA-11 (CA WA Restart Option) and JNODE. The CA-11 field contains the CA WA Restart Option subsystem name that controls this job. The JNODE field displays the JESNode where the job executed. These fields display this information only if you are running CA WA Restart Option r11.0 or newer and you have selected INSERT-RMS=Y (on the Job Definition panel) for the job you are submitting. If not, both field positions display *NA* (Not Applicable).

Note: For more information, see the CA WA Restart Option User Guide.

In previous releases of CA Workload Automation SE, the CA WA Restart Option interface was automatically disabled when it was unable to access the necessary modules. No message was issued indicating that this action occurred. In r11.3, a new message, CA-7.729, is written to the CA Workload Automation SE job log explicitly indicating the interface is disabled.