LSF Version 7.3 - Using Platform LSF HPC

Assume a host with 2 nodes, 2 CPUs per node (total of 4 CPUs)
When a job running within a cpuset that contains cpu 1 is suspended:
The job processes are detached from the cpuset and suspended
The cpuset is destroyed
When the job is resumed:
A cpuset with the same name is recreated
The processes are resumed and attached to the cpuset
The RESUME_OPTION parameter determines which CPUs are used to recreate the
cpuset:
◆ If RESUME_OPTION=ORIG_CPUS, only CPUs from the same nodes originally
used are selected.
◆ If RESUME_OPTION is not ORIG_CPUS LSF will first attempt to use cpus from
the original nodes to minimize memory latency. If this is not possible, any free CPUs
from the host will be considered.
If the job originally had a cpuset containing cpu 1, the possibilities when the job is
resumed are:
Viewing cpuset information for your jobs
The bacct -l, bjobs -l, and bhist -l commands display the following
information for jobs:
◆ CPUSET_TYPE=static | dynamic | none
◆ NHOSTS=number
◆ HOST=host_name
◆ CPUSET_NAME=cpuset_name
◆ NCPUS=num_cpus—the number of actual CPUs in the cpuset; can be greater than
the number of slots
bjobs -l 221
Job <221>, User <user1>, Project <default>, Status <DONE>, Queue <normal>, Com
mand <myjob>
Thu Dec 15 14:19:54: Submitted from host <hostA>, CWD <$HOME
>, 2 Processors Requested;
Thu Dec 15 14:19:57: Started on 2 Hosts/Processors <2*hostA>
, Execution Home </home/user1>, Execution CWD
</home/user1>;
Thu Dec 15 14:19:57: CPUSET_TYPE=dynamic;NHOSTS=1;HOST=hostA;CPUSET_NAME=
001
123
ORIG_CPUS 0 1
not ORIG_CPUS0123