LSF Version 7.3 - Administering Platform LSF

Understanding Job States
116 Administering Platform LSF
Exited jobs
An exited job ended with a non-zero exit status.
A job might terminate abnormally for various reasons. Job termination can happen
from any state. An abnormally terminated job goes into EXIT state. The situations
where a job terminates abnormally include:
◆ The job is cancelled by its owner or the LSF administrator while pending, or
after being dispatched to a host.
◆ The job is not able to be dispatched before it reaches its termination deadline,
and thus is aborted by LSF.
◆ The job fails to start successfully. For example, the wrong executable is specified
by the user when the job is submitted.
◆ The application exits with a non-zero exit code.
You can configure hosts so that LSF detects an abnormally high rate of job exit from
a host. See Handling Host-level Job Exceptions on page 98 for more information.
Post-execution states
Some jobs may not be considered complete until some post-job processing is
performed. For example, a job may need to exit from a post-execution job script,
clean up job files, or transfer job output after the job completes.
The DONE or EXIT job states do not indicate whether post-processing is complete,
so jobs that depend on processing may start prematurely. Use the
post_done and
post_err keywords on the bsub -w command to specify job dependency
conditions for job post-processing. The corresponding job states POST_DONE
and POST_ERR indicate the state of the post-processing.
After the job completes, you cannot perform any job control on the
post-processing. Post-processing exit codes are not reported to LSF.
See Chapter 36, “Pre-Execution and Post-Execution Commands” for more
information.