Reserving resources such as tape drives and other devices not directly configurable in LSF
Making job-starting decisions in addition to those directly supported by LSF
Customizing scheduling based on the exit code of a pre-execution command
Assigning jobs to run on specific processors on SMP machines
Modifying system configuration files before and after job execution
Using a post-execution command to clean up a state left by the pre-execution command or the job
Pre-execution and post-execution commands can be defined at the queue, application, and job levels.
The command path can contain up to 4094 characters for UNIX and Linux, or up to 255 characters for Windows, including the directory, file name, and expanded values for %J (job_ID) and %I (index_ID).
When JOB_INCLUDE_POSTPROC is defined in an application profile, a job is considered in RUN state while the job is in post exec stage (which is DONE state for regular jobs). When the job is also resizable, job grow requests are ignored. However job shrink requests can be processed. For either case, LSF does not invoke the job resized notification command.
Any executable command line can serve as a pre-execution or post-execution command. By default, the commands run under the same user account, environment, home directory, and working directory as the job. For parallel jobs, the commands run on the first execution host.