HP XC System 3.x Software - Manual (Page 115)

View the job:
$ bjobs -l 8
Job <8>, User , Project , Status , Queue ,
Interactive mode, Extsched , Command
date and time stamp: Submitted from host ,
CWD <$HOME>, 2 Processors Requested;
date and time stamp: Started on 2 Hosts/Processors
<2*lsfhost.localdomain>;
date and time stamp: slurm_id=24;ncpus=4;slurm_alloc=n[13-14];
date and time stamp: Done successfully. The CPU time used is 0.0 seconds.
SCHEDULING PARAMETERS:
r15s r1m r15m ut pg io ls it tmp swp mem
loadSched - - - - - - - - - - -
loadStop - - - - - - - - - - -
EXTERNAL MESSAGES:
MSG_ID FROM POST_TIME MESSAGE ATTACHMENT
0 - - - -
1 lsfadmin date and time SLURM[nodes=2] N
A.3.2 Example 2. Four Cores on Two Specific Nodes
This example submits a job that requests four cores on two specific nodes, on an XC system that has three
compute nodes.
Submit the job:
$ bsub -I -n4 -ext "SLURM[nodelist=n[14,16]]" srun hostname
Job <9> is submitted to default queue .
<>
<>
n14
n14
n16
n16
View the job:
$ bjobs -l 9
Job <9>, User , Project , Status ,
Queue , Interactive mode, Extsched ,
Command
date and time stamp: Submitted from host ,
CWD <$HOME>, 4 Processors Requested;
date and time stamp: Started on 4 Hosts/Processors
<4*lsfhost.localdomain>;
date and time stamp: slurm_id=24;ncpus=4;;
date and time stamp: Done successfully. The CPU time used is 0.0 seconds.
SCHEDULING PARAMETERS:
r15s r1m r15m ut pg io ls it tmp swp mem
loadSched - - - - - - - - - - -
loadStop - - - - - - - - - - -
EXTERNAL MESSAGES:
MSG_ID FROM POST_TIME MESSAGE ATTACHMENT
0 - - - -
1 lsfadmin date and time SLURM[nodelist=n[14,16]] N
View the job: 115