LSF Version 7.3 - Administering Platform LSF

Manage application profiles
374 Administering Platform LSF
4 Run badmin reconfig to reconfigure mbatchd.
Understanding
successful
application exit
values
Jobs that exit with one of the exit codes specified by SUCCESS_EXIT_VALUES in
an application profile are marked as DONE. These exit values are not be counted in
the EXIT_RATE calculation.
0 always indicates application success regardless of SUCCESS_EXIT_VALUES.
If both SUCCESS_EXIT_VALUES and REQUEUE_EXIT_VALUES are defined,
job will be set to PEND state and requeued.
SUCCESS_EXIT_VALUES has no effect on pre-exec and post-exec commands.
The value is only used for user jobs.
If the job exit value falls into SUCCESS_EXIT_VALUES, the job will be marked as
DONE. Job dependencies on done jobs behave normally.
For parallel jobs, the exit status refers to the job exit status and not the exit status of
individual tasks.
Exit codes for jobs terminated by LSF are excluded from success exit value even if
they are specified in SUCCESS_EXIT_VALUES.
For example. if SUCCESS_EXIT_VALUES=2 is defined, jobs exiting with 2 are
marked as DONE. However, if LSF cannot find the current working directory, LSF
terminates the job with exit code 2, and the job is marked as EXIT. The appropriate
termination reason is displayed by
bacct.
See Chapter 51, “Understanding Platform LSF Job Exit Information” for more
information about how LSF specifies exit codes for terminated jobs.
MultiCluster jobs
In the job forwarding model, for jobs sent to a remote cluster, jobs exiting with
success exit codes defined in the remote cluster are considered done successfully.
In the lease model, the parameters of
lsb.applications apply to jobs running on
remote leased hosts as if they are running on local hosts.