HCL Workload Automation, Version 9.4

Configuring the job status mapping policy

HCL Workload Automation calculates the status of an HCL Workload Automation job based on the PeopleSoft job Run Status and Distribution Status. In PeopleSoft, the run status monitors the running of the job until it reaches a final status; the distribution status monitors the status of the output of the job. If the final status of a PeopleSoft job is neither success nor warning, HCL Workload Automation ignores the distribution status and the HCL Workload Automation job status is ABEND.

If the final status of a PeopleSoft job is success or warning, you can decide whether to use the distribution status of the PeopleSoft job when determining the status of the HCL Workload Automation job by setting the PS_DISTSTATUS option in the options file:
0
The distribution status is ignored and the HCL Workload Automation job status is calculated as shown in Table 2.
1
The distribution status is used and the HCL Workload Automation job status is calculated as shown in Table 1. This is the default value.
Table 1 shows the relationship between the run status, the distribution status, and the HCL Workload Automation job status. The return code associated with the status is shown in parentheses. HCL Workload Automation uses this return code to evaluate the return code condition you specified in the Return Code Mapping Expression field in the Properties panel of the job definition. For more details about this field, refer to the online help by clicking the "?" in the top-right corner of the panel.
Table 1. Relationship between the run status, the distribution status, and the HCL Workload Automation job status
PeopleSoft job run status PeopleSoft job distribution status HCL Workload Automation job status
  • Success (9)
  • Warning (17)
  • Posted (5)
  • None (0)
 SUCC
  • Success (9)
  • Warning (17)
  • Not Posted (4)
  • Delete (6)
 ABEND
  • Success (9)
  • Warning (17)
  • Not Available (1)
  • Processing (2)
  • Generated (3)
  • Posting (7)
 EXEC
  • Cancel (1)
  • Delete (2)
  • Error (3)
  • Canceled (8)
  • No Success (10)
  • Blocked (18)
  • Restart (19)
 Any distribution status ABEND
Table 2 shows the relationship between the PeopleSoft run status and the HCL Workload Automation job status. The return code associated with the status is shown in parentheses. HCL Workload Automation uses this return code to evaluate the return code condition you specified in the Return Code Mapping Expression field in the Properties panel of the job definition. For more details about this field, refer to the online help by clicking the "?" in the top-right corner of the panel.
Table 2. Relationship between the run status and the HCL Workload Automation job status
PeopleSoft final run status HCL Workload Automation status
Cancel (1) ABEND
Delete (2) ABEND
Error (3) ABEND
Hold (4) WAIT
Queued (5) WAIT
Initiated (6) INIT
Processing (7) EXEC
Canceled (8) ABEND
Success (9) SUCC
No Success (10) ABEND
Pending (16) EXEC
Warning (17) SUCC
Blocked (18) ABEND
Restart (19) ABEND
Note: If HCL Workload Automation fails to retrieve the status of the PeopleSoft job, the HCL Workload Automation job status is DONE.
Parent topic: Defining PeopleSoft jobs