Platform LSF Reference Version 6.2

Environment Variables
Platform LSF Reference
277
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 the environment variable LSB_JOB_STARTER is properly defined,
sbatchd
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
See also
See “lsb.queues” under “JOB_STARTER” on page 412.
Example
◆ UNIX
The job starter is invoked from within a Bourne shell, making the command-line
equivalent:
/bin/sh -c "$LSB_JOB_STARTER command [argument...]"
where command [argument...] are the command line arguments you specified
in
lsrun, lsgrun, or ch.
If you define LSB_JOB_STARTER as follows:
% setenv LSB_JOB_STARTER "/bin/csh -c"
and run a simple C-shell job:
% lsrun "'a.out; echo hi'"
then 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:
LSB_JOB_STARTER command [argument...]
If you define LSB_JOB_STARTER as follows:
set LSB_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.
LSB_JOBEXIT_INFO
Syntax
LSB_JOBEXIT_INFO="SIGNAL signal_value signal_name"
Description
Contains information about signal that caused a job to exit.
Applies to post-execution commands. Post-execution commands are set with
POST_EXEC in
lsb.queues.