Administering Platform LSF - SAS

Chapter 30
External Job Submission and Execution Controls
Example
LSB_ESUB_METHOD=dce
(lsf.conf)
esub.dce
bsub -a fluent mesub esub
esub.fluent
In this example, esub.dce is defined as a mandatory esub, an esub already
exists in LSF_SERVERDIR, and the job is submitted as a FLUENT job to use
esub.fluent.
Configuring master esub and your application-specific esub
Naming your esub
Existing 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.
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
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).
esub.user is
reserved
The name esub.user is reserved for backward compatibility. Do not use the
name esub.user for your application-specific esub.
Administering Platform LSF 387