LSF Version 7.3 - Platform LSF Configuration Reference

With pre- and post-execution processing enabled at the queue or
application level
The following example illustrates how pre- and post-execution processing works for setting
the environment prior to job execution and for transferring resulting files after the job runs.
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.
Scope
Applicability
Details
Operating system
•
UNIX
•
Windows
•
A mix of UNIX and Windows hosts
Dependencies
•
UNIX and Windows user accounts must be valid on all hosts in the cluster and must
have the correct permissions to successfully run jobs.
•
On a Windows Server 2003, x64 Edition platform, users must have read and
execute privileges for cmd.exe.
Limitations
•
Applies to batch jobs only (jobs submitted using the bsub command)
Configuration to enable pre- and post-execution processing
The pre- and post-execution processing feature is enabled by defining at least one of the
parameters PRE_EXEC or POST_EXEC at the application or queue level, or by using the -E
option of the bsub command to specify a pre-execution command. In some situations,
specifying a queue-level or application-level pre-execution command can have advantages
over requiring users to use bsub -E. For example, license checking can be set up at the queue
Feature: Pre-execution and post-execution processing
Platform LSF Configuration Reference 37