Platform LSF Reference Version 6.2
Environment Variable Reference
Platform LSF Reference
288
Default
Undefined
Notes
Interactive Jobs
If you want to run an interactive job that requires some preliminary setup, LSF provides
a job starter function at the command level. A command-level job starter allows you to
specify an executable file that will run prior to the actual job, doing any necessary setup
and running the job when the setup is complete.
If LSF_JOB_STARTER is properly defined, RES will invoke the job starter (rather than
the job itself), supplying your commands as arguments.
Batch Jobs
A job starter can also be defined at the queue level using the JOB_STARTER parameter,
although this can only be done by the LSF administrator.
Where defined
From the command line
Example
◆
UNIX
The job starter is invoked from within a Bourne shell, making the command-line
equivalent:
/bin/sh -c "$LSF_JOB_STARTER command [argument...]"
where command [argument...] are the command line arguments you specified
in
lsrun, lsgrun, or ch.
If you define LSF_JOB_STARTER as follows:
% setenv LSF_JOB_STARTER "/bin/csh -c"
and run a simple C-shell job:
% lsrun "'a.out; echo hi'"
The following will be invoked to correctly start the job:
/bin/sh -c "/bin/csh -c 'a.out; echo hi'"
◆
Windows
RES runs the job starter, passing it your commands as arguments:
LSF_JOB_STARTER
command [argument...]
If you define LSF_JOB_STARTER as follows:
set LSF_JOB_STARTER=C:\cmd.exe /C
and run a simple DOS shell job:
C:\> lsrun dir /p
then the following will be invoked to correctly start the job:
C:\cmd.exe /C dir /p
See also
See “lsb.queues” under “JOB_STARTER” on page 412.
LSF_LIM_DEBUG
This parameter can be set from the command line or from lsf.conf.
See “lsf.conf” under “LSF_LIM_DEBUG” on page 554.