date and time stamp: Started on 4 Hosts/Processors <4*lsfhost.localdomain>;
date and time stamp:
Example
Example
$ bhist
Job <24>, User <lsfadmin>, Project <default>,
Interactive
Extsched <SLURM[nodes=4]>, Command </bin/bash>
date and time stamp: Submitted from host <n2>, to Queue <normal>, CWD <$HOME>,
4 Processors Requested, Requested Resources <type=any>;
date and time stamp: Dispatched to 4 Hosts/Processors <4*lsfhost.localdomain>;
date and time stamp: | ||||||
date and time stamp: | Done successfully. |
|
| |||
The CPU time used is | 0.1 seconds; |
|
|
| ||
date and time stamp: Post job process | done successfully; | |||||
Summary of time in seconds spent in various states by date and time stamp | ||||||
PEND | PSUSP | RUN | USUSP | SSUSP | UNKWN | TOTAL |
11 | 0 | 220 | 0 | 0 | 0 | 231 |
|
|
|
|
|
|
|
In particular, note the node and job allocation information provided in the above output:
date and time stamp: Dispatched to 4 Hosts/Processors <4*lsfhost.localdomain>;
date and time stamp:
10.11.2 Examining the Status of a Job
Once a job is submitted, you can use the bjobs command to track the job's progress. The bjobs command reports the status of a job submitted to LSF. By default, bjobs lists only the user's jobs that have not finished or exited.
The following are examples of bjobs command usage, and show the output it produces on an HP XC system. For more information about the bjobs command and its output, see the LSF manpages.
Example
Example
$ bjobs 24 |
|
|
|
|
| |
JOBID | USER | STAT QUEUE | FROM_HOST EXEC_HOST | JOB_NAME | SUBMIT_TIME | |
24 | msmith | RUN normal | n16 | lsfhost.localdomain | /bin/bash | date and time |
|
|
|
|
|
|
|
As shown in the previous output, the bjobs command returns information that includes the job id, user name, job status, queue name, submitting host, executing host, job name, and submit time. In this example, the output shows that job /bin/bash was submitted from node n16 and launched on the execution host (lsfhost.localdomain).
98 Using LSF