LSF Version 7.3 - Using Platform LSF HPC

Simple job script modifications
The following example shows how to convert the POE options in a Load Leveler
command file to LSF options in your job scripts for a non-shared US or IP job.
◆ Only one job at a time can run on a non-shared node
◆ An IP job can share a node with a dedicated US job (-adapter_use is dedicated)
◆ The POE job always runs one task per CPU, so the -cpu_use option is not used
This example uses following POE job script to run an executable named mypoejob:
#!/bin/csh
#@ shell = /bin/csh
#@ environment = ENVIRONMENT=BATCH; COPY_ALL;\
# MP_EUILIB=us; MP_STDOUTMODE=ordered; MP_INFOLEVEL=0;
#@ network.MPI = switch,dedicated,US
#@ job_type = parallel
#@ job_name = batch-test
#@ output = $(job_name).log
#@ error = $(job_name).log
#@ account_no = USER1
#@ node = 2
#@ tasks_per_node = 8
#@ node_usage = not_shared
#@ wall_clock_limit = 1:00:00
#@ class = batch
notify_user Set in lsf.conf
output bsub -o
parallel_path Y
preferences bsub -R "select[...]
queue bsub -q
requirements bsub -R and -m
resources bsub -R Set rusage for each task according to
the Load Leveler equivalent
rss_limit bsub -M
shell Y
stack_limit bsub -S
startdate bsub -b
step_name Y
task_geometry Use the
LSB_PJL_TASK_GEOMETRY
environment variable to specify task
geometry for your jobs.
LSB_PJL_TASK_GEOMETRY
overrides any mpirun n option.
total_tasks bsub -n
user_priority bsub -sp
wall_clock_limit bsub -W