Exit Code 9 Set To Success But Job Still Failed

Document ID : KB000044063
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction: 

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.

Question: 

Why was the setting for the exit code interpretation ignored?

Environment:  

CAWA DE server, CAWA Agent for unix/linux

Answer: 

 

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.