A JOBS runs Unix commands (sh, jar) that end with RETCODE=00 on the OS level, but in the Automation Engine the result is error code 1.

Document ID : KB000087750
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
U2000009 Job 'job name' with RunID '29209861' ended with return code '1'.

A JOBS runs Unix commands (or sh, jar ...) that end with returncode 0 on the OS level, but in the Automation Engine the result is error code 1.
 
U2000009 Job 'SOA.SOA_MONITOR' with RunID '29209861' ended with return code '1'.

All JOBS execute just Linux-commands like ls or call sh-scripts or jar-files. They all succeed (display of the return code with echo $? shows 0) on Linux side. Nevertheless, they Automic job ends with an error code ≠ 0.
Cause:
Cause type:
Other
Root Cause: Different inheritance of user rights by different Linux-shells
Resolution:
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Version(s):
N/A
Additional Information:
Workaround :
Changing Shell to ksh in the Linux job might help here, as the different shells have different inheritance-mechanisms. Or try another shell to find one that works.If you give no input for field Shell in the UNIX-tab, the shell defined for the user in the login-object is used. By giving a shell in this field, you force the agent to use this shell for the job.