LSF Version 7.3 - Using Platform LSF HPC

Load Leveler directives
Load Leveler job commands are handled as follows:
◆ Ignored by LSF
◆ Converted to bsub options (or queue options in lsb.queues)
◆ Require special handling in your job script
Cannot convert to LSF. You
must use span[host=1]
bsub -n a*b -R "span[ptile=b]"
◆ Only use if the poe options are:
poe -nodes a -tasks_per_nodes b -nodes b
bsub -n a*b -R "span[ptile=b]"
◆ Only use if the poe options are:
poe -nodes a -tasks_per_nodes b -procs
a*b
account_no Y Use LSF accounting.
arguments Y Place job arguments in the job
command line
blocking bsub -n with span[ptile]
all checkpoint
commands
Y
class bsub -P or -J
comment Y
core_limit bsub -C
cpu_limit bsub -c or -n
data_limit bsub -D
dependency bsub -w
environment Set in job script or in esub.poe
error bsub -e
executable Y Enter the job name in the job script
file_limit bsub -F
group Y
hold bsub -H
image_size bsub -v or -M
initialdir Y The working directory is the current
directory
input bsub -i
job_cpu_limit bsub -c
job_name bsub -J
job_type Y Handled by esub.poe
max_processors bsub -n min, max
min_processors bsub -n min, max
network bsub -R
node combinations See “-nodes combinations” on page 94
notification Set in lsf.conf