LSF Version 7.3 - Administering Platform LSF

Using esub
574 Administering Platform LSF
Interactive remote execution
Interactive remote execution also runs esub and eexec if they are found in
LSF_SERVERDIR. For example,
lsrun invokes esub, and RES runs eexec before
starting the task.
esub is invoked at the time of the ls_connect(3) call, and RES
invokes
eexec each time a remote task is executed. RES runs eexec only at task
startup time.
DCE credentials and AFS tokens
esub and eexec are also used for processing DCE credentials and AFS tokens. See
the following documents on the Platform Web site for more information:
◆ “Installing LSF on AFS”
◆ “Installing LSF on DCE/DFS”
Using esub
About esub
An esub, short for external submission, is a user-written executable (binary or
script) that can be used to validate, modify, or reject jobs. The
esub is put into
LSF_SERVERDIR (defined in
lsf.conf) where LSF checks for its existence when
a job is submitted, restarted, and modified. If LSF finds an
esub, it is run by LSF.
Whether the job is submitted, modified, or rejected depends on the logic built into
the
esub.
Any messages that need to be provided to the user should be directed to the
standard error (
stderr) stream and not the standard output (stdout) stream.
In this section ◆ Environment variables to bridge esub and LSF on page 574
◆ General esub logic on page 577
◆ Rejecting jobs on page 578
◆ Validating job submission parameters on page 578
◆ Modifying job submission parameters on page 579
◆ Using bmod and brestart commands with mesub on page 579
◆ Use multiple esub (mesub) on page 580
◆ How master esub invokes application-specific esubs on page 580
◆ Configure master esub and your application-specific esub on page 581
Environment variables to bridge esub and LSF
LSF provides the following environment variables in the esub execution
environment:
LSB_SUB_PARM_FILE
This variable points to a temporary file containing the job parameters that esub
reads when the job is submitted. The submission parameters are a set of name-value
pairs on separate lines in the format "option_name=value".
The following option names are supported: