HP XC System Software Administration Guide Version 4.0

You can use the -l (long) option to obtain detailed information about a job, as shown in this
example:
$ bjobs -l 116
Job <116>, User <lsfadmin>, Project default, Status <RUN>, Queue <normal>, Co
mmand <srun sleep 50>
date time: Submitted from host <lsfhost.localdomain>, CWD <$HOME>, Ou
tput File <./>, 8 Processors Requested;
date time: Started on 8 Hosts/Processors <8*lsfhost.localdomain>, Exe
cution Home <hptc_cluster/hptc_cluster>, Execution CWD <hptc/hptc;
_cluster/lsf/home>;
date time: slurm_id=7;ncpus=8;slurm_alloc=n[1-4];
SCHEDULING PARAMETERS:
r15s r1m r15m ut pg io ls it tmp swp mem
loadSched - - - - - - - - - - -
loadStop - - - - - - - - - - -
Note the output that identifies the SLURM_JOBID and the SLURM allocation:
date time: slurm_id=7;ncpus=8;slurm_alloc=n[1-4];
You can use the SLURM_JOBID with various SLURM commands, for example, use the squeue
command to view information about jobs in the SLURM scheduling queue and use the scontrol
show command to display the state of the job.
$ bsub -n6 srun date
Job <154> is submitted to default queue <normal>
.
.
.
$ bjobs -l 154 | grep slurm_id
date and time: slurm_id=995;ncpus=6;slurm_alloc=n[14-16];
.
.
.
$ scontrol show job 995
JobId=995 UserId=lsfadmin(501) GroupId=lsfadmin(501)
Name=LSFclustername@LSF_JOBID
Priority=4294900775 Partition=lsf BatchFlag=0
AllocNode:Sid=n16:24657 TimeLimit=UNLIMITED ExitCode=0:0
JobState=CANCELLED StartTime=10/30-00:35:44 EndTime=10/30-00:36:16
NodeList=n[14-16] NodeListIndices=
AllocCPUs=2*3
ReqProcs=3 ReqNodes=3 ReqS:C:T=1-65535:1-65535:1-65535
Shared=1 Contiguous=0 CPUs/task=0
MinProcs=1 MinSockets=1 MinCores=1 MinThreads=1
MinMemory=1 MinTmpDisk=0 Features=(null)
Dependency=0 Account=(null) Reason=None Network=(null)
ReqNodeList=n[14-16] ReqNodeListIndices=0-2
ExcNodeList=(null) ExcNodeListIndices=
SubmitTime=10/30-00:35:44 SuspendTime=None PreSusTime=0
The NAME= output of the scontrol show command returns the name of the LSF cluster (the
installation default is hptclsf) and the LSF with SLURM job number, separated by the at
character (@).
The bhist command reports the history of a job.
After you have gathered information about a job, you can use other useful LSF commands to
control LSF with SLURM jobs: bkill, bstop, and bresume.
The bkill command kills a running job. This command uses the SLURM scancel command.
The bstop command suspends the execution of a running job.
The bresume command resumes the execution of a suspended job.
For more information, see bkill(1), bstop(1), and bresume(1).
16.8 Monitoring and Controlling LSF with SLURM Jobs 199