PBS Exit Status

To interpret the signal contained in the exit status value, subtract the base value from the exit status. For example, if a job had an exit status of 143, that indicates the job was killed via a SIGTERM (e.g. 143 - 128 = 15, signal 15 is SIGTERM). See the kill(1) manual page for a mapping of signal numbers to signal names.

If Exit Status = 0

This indicates that the job executed successfully.

If 0 <= Exit Status < 128

(or 256 depending on the system)

This is the exit value of the top process in the job, typically the shell. This may be the exit value of the last command executed in the shell or the .bash_logout script if the user has such a script.

If Exit Status >= 128

(or 256 depending on the system)

This means the job was killed with a signal. The signal is given by X modulo 128 (or 256). For example an exit value of 137 means the job’s top process was killed with signal 9 (137 % 128 = 9).

0
1       Catchall for general errors
126     Command invoked cannot execute
127     "command not found"
143     128 + 15 SIGTERM = 143
254
265     265 % 128    9 = SIGKILL
271     271 % 128   15 = SIGTERM

Examples:

Exit_status = 271
=>> PBS: job killed: walltime 152 exceeded limit 120

http://tldp.org/LDP/abs/html/exitcodes.html

http://www.bu.edu/tech/files/text/batchcode.txt

http://tx.technion.ac.il/doc/tamnun/PBS%20exit%20codes.html https://dl.technion.ac.il/docs/cis/public/usg/tamnun/PBS%20exit%20codes.html

http://wiki.chpc.ac.za/howto:gpu_gromacs#pbs_job_script

http://wiki.chpc.ac.za/howto:gromacs

https://www.nas.nasa.gov/hecc/support/kb/pbs-exit-codes_185.html

https://2021.help.altair.com/2021/accelerator/html/ft/topics/ft/exit_status.htm

How to interpret the PBS exit codes: https://opus.nci.org.au/display/Help/How+to+interpret+the+PBS+exit+codes

Example of exit code from C program: http://docs.adaptivecomputing.com/torque/archive/3-0-2/2.7jobexitstatus.php