Mapping between HCL Workload Automation and IBM InfoSphere DataStage job statuses
Map HCL Workload Automation job status to IBM InfoSphere DataStage job status to understand their processing.
Table 1 table shows how
you can map the HCL Workload Automation job
status to the IBM InfoSphere DataStage job
status based on the return code you find in the job log output.
| IBM InfoSphere DataStage job return code | IBM InfoSphere DataStage command line job status | IBM InfoSphere DataStage director job status | Dynamic Workload Console and Application Lab job status | HCL Workload Automation job status | IBM Workload Scheduler for z/OS job status |
|---|---|---|---|---|---|
| 0 | RUNNING | Running | Running | EXEC | Executing |
| 1 | RUN OK | Finished | Successful | SUCC | Completed |
| 2 | RUN with WARNINGS | Finished (see log) | Successful | SUCC | Completed |
| 3 | RUN FAILED | Abort Error | Error | ABEND | Error |
| 96 | UNKNOWN | Crashed | Error | ABEND | Error |
| 97 | STOPPED | Stopped | Error | ABEND | Error |
| 98 | NOT RUNNABLE | Not compiled | Error | FAILED | Error |
Any other return code or status you find in the IBM InfoSphere DataStage log generated either by using the IBM InfoSphere DataStage command line or the IBM InfoSphere DataStage Directory interface, is mapped to error if you are using the Dynamic Workload Console or to FAILED if you are using the HCL Workload Automation command line.