LSF Version 7.3 - Platform LSF Configuration Reference

Executable file UNIX naming convention Windows naming convention
esub LSF_SERVERDIR/
esub.application
LSF_SERVERDIR
\esub.application.exe
LSF_SERVERDIR
\esub.application.bat
eexec LSF_SERVERDIR/eexec LSF_SERVERDIR\eexec.exe
LSF_SERVERDIR\eexec.bat
The name of your esub should indicate the application with which it runs. For example:
esub.fluent.
Restriction:
The name esub.user is reserved. Do not use the name
esub.user for an application-specific esub.
Valid file names contain only alphanumeric characters,
underscores (_), and hyphens (-).
Once the LSF_SERVERDIR contains one or more esub executables, users can specify the
esub executables associated with each job they submit. If an eexec exists in
LSF_SERVERDIR, LSF invokes that eexec for all jobs submitted to the cluster.
The following esub executables are provided as separate packages, available from Platform
Computing Inc. upon request:
•
esub.openmpi : OpenMPI job submission
•
esub.pvm: PVM job submission
•
esub.poe : POE job submission
•
esub.ls_dyna : LS-Dyna job submission
•
esub.fluent : FLUENT job submission
•
esub.afs or esub.dce: AFS or DCE security
•
esub.lammpi LAM/MPI job submission
•
esub.mpich_gm : MPICH-GM job submission
•
esub.intelmpi: Intel
®
MPI job submission
•
esub.bproc: Beowulf Distributed Process Space (BProc) job submission
•
esub.mpich2: MPICH2 job submission
•
esub.mpichp4: MPICH-P4 job submission
•
esub.mvapich: MVAPICH job submission
•
esub.tv, esub.tvlammpi, esub.tvmpich_gm, esub.tvpoe: TotalView
®
debugging
for various MPI applications.
Environment variables used by esub
When you write an esub, you can use the following environment variables provided by LSF
for the esub execution environment:
LSB_SUB_PARM_FILE
Points to a temporary file that LSF uses to store the bsub options entered in the
command line. An esub reads this file at job submission and either accepts the values,
Feature: External job submission and execution controls
72 Platform LSF Configuration Reference