HCL Workload Automation, Version 9.4

Agent availability versus job availability

Having HCL Workload Automation working in a Windows cluster and HACMP for AIX environments does not mean that the jobs the scheduler launches are automatically aware of the cluster. It is not the responsibility of HCL Workload Automation to roll back any actions that a job might have performed during the time it was running. It is the responsibility of the user creating the script or command to allow for a roll back or recovery action in case of failover.

For a failover, the HCL Workload Automation agent reports any job running at that moment in the ABEND state with return code RC=0. This prevents any further dependencies being released. Only a recovery (or rerun) of the failing jobs is possible.

In general, HCL Workload Automation does not manage job and job stream interruption. Extra logic needs to be added by the user to recover job and job stream interruptions (see sections 1.4.2 and 2.3.4 of the Redbook High Availability Scenarios with IBM® Workload Scheduler and IBM Tivoli® Framework).