Interpreting PBS Exit Codes

The PBS Server logs and accounting logs record an 'exit status' of jobs.
Zero or positive exit status is the status of the top level shell.
Certain negative exit status are used internally and will never be reported to the user.
The positive exit status values indicate which signal killed the job.
Depending on the system, values greater than 128 (or on some systems 256, see wait(2) or waitpid(2) for more information) are the value of the signal that killed the job.
To interpret (or 'decode') 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 jobs 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 name on your operating system.

Job Termination

The exit code from a batch job is a standard Unix termination signal.
Typically, exit code 0 means successful completion.
Codes 1-127 are generated from the job calling exit() with a non-zero value to indicate an error.
Exit codes 129-255 represent jobs terminated by Unix signals.
Each signal has a corresponding value which is indicated in the job exit code.

Job Termination Signals

NOTE : Consult the signal(7) man page for a complete list of signals.

Job Exit Status

Interpreting PBS Error Codes

The error returns possible to a Batch Request (qstat, qdel, qsub)

 * Each error is prefixed with the string PBSE_ for Portable (Posix)
 * Batch System Error.  The numeric values start with 15000 since the
 * POSIX Batch Extensions Working group is 1003.15

PBS ERROR CODES