LSF Version 7.3 - Platform LSF Configuration Reference

Post-execution command behavior
A post-execution command runs after the job finishes, regardless of the exit state of the job.
Once a post-execution command is associated with a job, that command runs even if the job
fails. You cannot configure the post-execution command to run only under certain conditions.
The resource usage of post-execution processing is not included in the job resource usage
calculation, and post-execution command exit codes are not reported to LSF.
If POST_EXEC=$USER_POSTEXEC in either lsb.applications or lsb.queues, UNIX
users can define their own post-execution commands:
setenv USER_POSTEXEC /path_name
where the path name for the post-execution command is an absolute path.
If POST_EXEC=$USER_POSTEXEC and …
Then …
The user defines the USER_POSTEXEC environment
variable
•
LSF runs the post-execution command defined by the
environment variable USER_POSTEXEC
•
After the user-defined command runs, LSF reports
successful completion of post-execution processing
•
If the user-defined command fails, LSF reports a failure
of post-execution processing
The user does not define the USER_POSTEXEC
environment variable
•
LSF reports successful post-execution processing
without actually running a post-execution command
Important:
Do not allow users to specify a post-execution command when
the pre- and post-execution commands are set to run under the
root account.
Configuration to modify pre- and post-execution processing
Configuration parameters modify various aspects of pre- and post-execution processing
behavior by:
•
Preventing a new job from starting until post-execution processing has finished
•
Controlling the length of time post-execution processing can run
•
Specifying a user account under which the pre- and post-execution commands run
•
Controlling how many times pre-execution retries
Configuration to modify when new jobs can start
When a job finishes, sbatchd reports a job finish status of DONE or EXIT to mbatchd. This
causes LSF to release resources associated with the job, allowing new jobs to start on the
execution host before post-execution processing from a previous job has finished.
In some cases, you might want to prevent the overlap of a new job with post-execution
processing. Preventing a new job from starting prior to completion of post-execution
processing can be configured at the application level or at the job level.
At the job level, the bsub -w option allows you to specify job dependencies; the keywords
post_done and post_err cause LSF to wait for completion of post-execution processing before
starting another job.
Feature: Pre-execution and post-execution processing
Platform LSF Configuration Reference 41