Platform LSF Administration Guide Version 6.2

Chapter 33
External Job Submission and Execution Controls
Administering Platform LSF
501
Example
In this example:
◆ esub.dce is defined as the only mandatory esub
◆ An executable named esub already exists in LSF_SERVERDIR
◆ Executables named esub.fluent and esub.license exist in
LSF_SERVERDIR
◆ bsub -a fluent license submits the job as a FLUENT job, and mesub
invokes the following esub executables in LSF_SERVERDIR in this order:
a esub.dce
b esub
c esub.fluent
d esub.license
◆ bsub without the -a option submits the job, and mesub invokes only the
mandatory
esub.dce and the existing esub in LSF_SERVERDIR, not the
application-specific
esub programs.
Configuring master esub and your application-specific esub
The master esub is installed as LSF_SERVERDIR/mesub. After installation:
1 Create your own application-specific esub.
2 Optional. Configure LSB_ESUB_METHOD in lsf.conf to specify a mandatory
esub for all job submissions.
Naming your esub
Use the following naming conventions:
◆ On UNIX, LSF_SERVERDIR/esub.application
For example, esub.fluent for FLUENT jobs
◆ On Windows, LSF_SERVERDIR\esub.application.[exe |bat]
For example, esub.fluent.exe
The name of the esub program must be a valid file name. It can contain only
alphanumeric characters, underscore (
_) and hyphen (-).
Existing esub
Your existing esub does not need to follow this convention and does not need to be
renamed. However, since mesub invokes any esub that follows this convention, you
should move any backup copies of your esubs out of LSF_SERVERDIR or choose a
name that does not follow the convention (for example, use esub_bak instead of
esub.bak).
(lsf.conf)
LSB_ESUB_METHOD=dce
bsub -a fluent license mesub
esub
esub.fluent
esub.dce
LSF_SERVERDIR
esub.license