Command Reference Guide

Platform LSF Command Reference 179
Sets the user’s execution environment for the job, including the current working
directory, file creation mask, and all environment variables, and sets LSF
environment variables before starting the job.
When a job is run, the command line and
stdout/stderr buffers are stored in the
directory home_directory
/.lsbatch on the execution host. If this directory is not
accessible,
/tmp/.lsbtmp user_ID is used as the job’s home directory. If the current
working directory is under the home directory on the submission host, then the
current working directory is also set to be the same relative directory under the
home directory on the execution host.
By default, if the current working directory is not accessible on the execution host,
the job runs in
/tmp. If the environment variable
LSB_EXIT_IF_CWD_NOTEXIST is set to Y and the current working directory is
not accessible on the execution host, the job exits with the exit code 2.
If no command is supplied,
bsub prompts for the command from the standard
input. On UNIX, the input is terminated by entering CTRL-D on a new line. On
Windows, the input is terminated by entering CTRL-Z on a new line.
To kill a batch job submitted with
bsub, use bkill.
Use
bmod to modify jobs submitted with bsub. bmod takes similar options to bsub.
Jobs submitted to a chunk job queue with the following options are not chunked;
they are dispatched individually:
◆ -I (interactive jobs)
◆ -c (jobs with CPU limit greater than 30)
◆ -W (jobs with run limit greater than 30 minutes)
To submit jobs from UNIX to display GUIs through Microsoft Terminal Services
on Windows, submit the job with bsub and define the environment variables
LSF_LOGON_DESKTOP=1 and LSB_TSJOB=1 on the UNIX host. Use
tssub to
submit a Terminal Services job from Windows hosts. See Using Platform LSF on
Windows for more details.
If the parameter LSB_STDOUT_DIRECT in
lsf.conf is set to Y or y, and you use
the
-o or -oo option, the standard output of a job is written to the file you specify
as the job runs. If LSB_STDOUT_DIRECT is not set, and you use
-o or -oo, the
standard output of a job is written to a temporary file and copied to the specified
file after the job finishes. LSB_STDOUT_DIRECT is not supported on Windows.
Default Behavior
LSF assumes that uniform user names and user ID spaces exist among all the hosts
in the cluster. That is, a job submitted by a given user runs under the same user’s
account on the execution host. For situations where nonuniform user names and
user ID spaces exist, account mapping must be used to determine the account used
to run a job.
bsub uses the command name as the job name. Quotation marks are significant.
Options related to file names and job spooling directories support paths that
contain up to 4094 characters for UNIX and Linux, or up to 255 characters for
Windows.