LSF Version 7.3 - Using Platform LSF HPC

# Copy output data from $WORKDIR to appropriate archive FS,
# since we are currently running within a volatile
# "scratch" filesystem.
# Clean unneeded files from $WORKDIR after job ends.
rm -f $WORKDIR/mpihello
echo "Job completed at: `date`"
# End script ---------
Submit the job script as a redirected job, specifying the appropriate resource
requirement string:
bsub -R "select[adapter_windows>0] rusage[adapter_windows=1] span[ptile=8]" <
mypoe_jobscript
Compare the job script submission with the equivalent job submitted with all the LSF
options on the command line:
bsub -x -a poe -q hpc_ibm -n 16 -R "select[adapter_windows>0]
rusage[adapter_windows=1] span[ptile=8]" mpirun.lsf mypoejob -euilib us
To submit the same job as an IP job, substitute ip for us, and remove the select and
rusage statements:
bsub -x -a poe -q hpc_ibm -n 16 -R "span[ptile=8]" mpirun.lsf mypoejob
-euilib ip
To submit the job as a shared US or IP job, remove the bsub -x option from the job
script or command line. This allows other jobs to run on the host your job is running on:
bsub -a poe -q hpc_ibm -n 16 -R "span[ptile=8]" mpirun.lsf mypoejob -euilib us
or
bsub -a poe -q hpc_ibm -n 16 -R "span[ptile=8]" mpirun.lsf mypoejob -euilib ip
Advanced job script modifications
If your environment runs any of the following:
◆ A mix of IP and US jobs,
◆ A combinations of dedicated and shared -adapter_use
◆ Unique and multiple -cpu_use
your job scripts must use the us_tasks and dedicated_tasks LSF resources.
#@ environment = ENVIRONMENT=BATCH; MP_EUILIB=us setenv ENVIRONMENT BATCH
setenv MP_EUILIB=us
#@wall_clock_limit = 1:00:00 #BSUB - W 60
#@ output = $(job_name).log #BSUB -o batch_test.%J_%I.out
#@ error = $(job_name).log #BSUB -e batch_test.%J_%I.err
#@node =2
#@tasks_per_node =8
#BSUB -n 16 -R "span[ptile=8]"
# Execute programs:
poe mypoejob
poe $WORKDIR/mpihello
#Execute programs:
mpirun.lsf mypoejob -euilib us
mpirun.lsf $WORKDIR/mpihello -euilib us