🚨 AutoSys Exit Codes Reference

Common AutoSys and OS-level job exit codes with resolutions

📘 About Exit Codes

AutoSys Workload Automation reports exit codes to indicate the success or failure of jobs. A code of 0 typically means success. Non-zero or negative codes point to errors, system issues, or agent problems.

🚫 Internal AutoSys Exit Codes

📋 Common Exit Codes Reference Table & Fixes

Exit Code Meaning Solution / Comments
0 Success No action needed
1 General error (e.g., divide by zero, unknown function) Check syntax or operations in script
2 Shell misuse, missing keyword or command Check shell compatibility and syntax
5 Access Denied (Windows) Add oscomponent.logon.elevated=true to agentparm.txt
9 Job killed due to TERM_RUN_TIME Review runtime and rerun if needed
12 Low memory or swap space issue Increase swap, reboot server, raise ulimit -u
15 Job terminated (e.g., reboot) Often due to system shutdown or missing drive
28 No space left on device Check disk space and inode usage with df -h and df -i
126 Command not executable Check script permissions and file type
127 Command not found Check PATH variable or command typo
128 Invalid argument to exit Use only numbers 0–255
128+n Fatal error signal n (e.g. 137 = kill -9) Check if process was forcefully killed
130 Terminated by Control-C User manually interrupted with Ctrl+C
132 Illegal instruction (AIX SED) Disable Stack Execution Disable (SED) for cybAgent
183 File already exists Use session config params like oscomponent.su.newconsole=true
255 Exit status out of range Allow negative exit with oscomponent.cmpc.negative=true
-655 Too many restart attempts Check max_restart_count settings
-656 Job not started or in progress Job stuck — may require restart
-657 RUNNING but no job process found Run chase -E -A to verify
1314 Insufficient privileges (Windows) Set oscomponent.logon.elevated=true
1326 Logon failure: bad credentials Verify user/password in autosys_secure
4014 Shell verification failed Match script shell with valid shell list in agentparm.txt
4030 Inode issue on server Use df -i to check inode usage
20003 FILEWATCHER killed via KILLJOB Rerun the job
20004 Error redirecting std_in_file Ensure file exists and is accessible
20005 Error redirecting std_out_file Check path and write permissions
20007 Command file not found Add:
oscomponent.lookupcommand=true
oscomponent.cmdprefix.force=true
FFFFFFFF Negative exit code Enable oscomponent.cmpc.negative=true