HP XC System 4.x Software manual Getting Job Allocation Information, Than what the job requests

on this topic. See the LSF manpages for full information about the commands described in this section.

The following LSF commands are described in this section:

bjobs “Examining the Status of a Job”

bhist “Viewing the Historical Information for a Job”

10.11.1 Getting Job Allocation Information

Before a job runs, LSF integrated with SLURM allocates SLURM compute nodes based on job resource requirements.

After LSF integrated with SLURM allocates nodes for a job, it attaches allocation information to the job.

The bjobs -lcommand provides job allocation information on running jobs. The bhist -lcommand provides job allocation information for a finished job. For details about using these commands, see the LSF manpages .

A job allocation information string resembles the following:

slurm_id=slurm_jobid;ncpus=slurm_nprocs;slurm_alloc=node_list

This allocation string has the following values:

slurm_id	SLURM_JOBID environment variable. This is SLURM allocation ID (Associates
	LSF job with SLURM allocated resources.)
ncpus	SLURM_NPROCS environment variable. This the actual number of allocated
	cores. Under node-level allocation scheduling, this number may be bigger
	than what the job requests.)
slurm_alloc	A comma separated list of allocated nodes.

LSF integrated with SLURM sets the SLURM_JOBID and SLURM_NPROCS environment variables, when it starts a job.

Example 10-3illustrates how to use the the bjobs -lcommand to obtain job allocation information about a running job:

Example 10-3 Job Allocation Information for a Running Job

$ bjobs -l 24

Job <24>, User <lsfadmin>, Project <default>, Status <RUN>, Queue <normal>, Interactive pseudo-terminal shell mode, Extsched <SLURM[nodes=4]>, Command </bin/bash>

date and time stamp: Submitted from host <n2>, CWD <$HOME>,

4 Processors Requested, Requested Resources <type=any>; date and time stamp: Started on 4 Hosts/Processors <4*lsfhost.localdomain>; date and time stamp: slurm_id=22;ncpus=8;slurm_alloc=n[5-8];

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			stamp		SLURM[nodes=4]			N

In particular, note the node and job allocation information provided in the above output:

10.11 Getting Information About Jobs 97