Exit Code 9 Set To Success But Job Still Failed
search cancel

Exit Code 9 Set To Success But Job Still Failed


Article ID: 44063


Updated On:


DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)


A unix job in the DE server was created with the exit code 9 to be interpreted as for the success.

However, despite the job was finished with the code 9, its state was displayed as FAILED.

Why was the setting for the exit code interpretation ignored?


Release: WKLOEB01300-11.3-Workload Automation-Agent for Oracle EBusiness Ste

CAWA DE server, CAWA Agent for unix/linux


In particular, the code 9 was generated by the SIGKILL, i.e. the job was finished abnormally - this condition you could read in the Status field of the job details.

Then, it was the way the agent behaves: the agent makes an OS system call to determine if the process exited normally; if it exited abnormally, e.g. after kill -9 (SIGKILL), the code sets the response to FAILED and such exit codes are not evaluated to determine success or failure - this is only done if the job terminates normally.