Platform LSF Administration Guide Version 6.2

Understanding External Executables
Administering Platform LSF
494
Understanding External Executables
About esub and eexec
LSF provides the ability to validate, modify, or reject job submissions, modify execution
environments, and pass data from the submission host directly to the execution host
through the use of the
esub and eexec executables. Both are site-specific and user
written and must be located in LSF_SERVERDIR.
Validate, modify,
or reject a job
To validate, modify, or reject a job, an esub needs to be written. See “Using esub” on
page 495
Modifying
execution
environments
To modify the execution environment on the execution host, an eexec needs to be
written. See “Working with eexec” on page 503
Passing data
To pass data directly to the execution host, an esub and eexec need to be written. See
“Using esub and eexec to pass data to execution environments” on page 503
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”