LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 581
External Job Submission and Execution Controls
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:
❖ esub.dce
❖ esub
❖ esub.fluent
❖ 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.
Configure 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.
Name your esub
1 Use the following naming conventions:
❖ On UNIX, LSF_SERVERDIR/esub.application
❖ On Windows, LSF_SERVERDIR\esub.application.[exe |bat]
For FLUENT jobs, for example:
◆ UNIX: esub.fluent
◆ Windows: esub.fluent.exe