LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 725
C HAPTER
51
Understanding Platform LSF Job Exit
Information
Contents
◆ Why did my job exit? on page 725
◆ How LSF translates events into exit codes on page 725
◆ Application and system exit values on page 726
◆ LSF job termination reason logging on page 728
◆ Job termination by LSF exit information on page 731
◆ LSF RMS integration exit values on page 733
Why did my job exit?
LSF collects job information and reports the final status of a job. Traditionally jobs
finishing normally report a status of 0, which usually means the job has finished
normally. Any non-zero status means that the job has exited abnormally.
Most of the time, the abnormal job exit is related either to the job itself or to the
system it ran on and not because of an LSF error. This document explains some of
the information LSF provides about the abnormal job termination.
How LSF translates events into exit codes
The following table summarizes LSF exit behavior for some common error
conditions.
Error codition LSF exit code Operating system System exit code
equivalent
Meaning
Command not found 127 all 1 or 127 Command shell returns 1 if command
not found. If the command cannot be
found inside a job script, LSF return
exit code 127.
Directory not available
for output
0 all 1 LSF sends the output back to user
through email if directory not available
for output (bsub -o).