HP XC System Software Administration Guide Version 2.1

Example 12 -2 is a similar example but twenty pro c
essors are reserved.
Example 12-2: Launching Another Job Without the JOB_STARTER Script
Configured
$ bsub -I -n20 hostname
Job <21> is submitted to default queue <normal>.
<<Waiting for dispatch...>>
<<starting on lsfhost.localdomain>>
n120
In both the previous examples, processors were reserved but not used. To ensure that a job is
launched prop erly on the reserved nodes without the JOB_STARTER script configured, the
user must preface each command with either the srun com mand or the mpirun -srun
command, as show n in Example 12-3 and Example 12-4.
Example 12-3: Launching a Job Successfully Without the JOB_STARTER Script
using srun
$ bsub -I srun hostname
Job <22> is submitted to default queue <normal>.
<<Waiting for dispatch...>>
<<starting on lsfhost.localdomain>>
n99
Example 12-4: Launching a Job Successfully Without the JOB_STARTER Script
Using mpirun
$ bsub -I -n4 mpirun -srun hostmpi
Job <23> is submitted to default queue <normal>.
<<Waiting for dispatch...>>
<<starting on lsfhost.localdomain>>
task 0 running on n1
task 1 running on n1
task 2 running on n2
task 3 running on n2
Example 12-5 illustrates launching the same job as in Example 12-1, but with the
JOB_STARTER script con figured.
Example 12-5: A Basic Job Launch with the JOB_S
TARTER Script Configured
$ bsub -I hostname
Job <24> is submitted to default queue <normal>.
<<Waiting for dispatch...>>
<<starting on lsfhost.localdomain>>
n99
12.7 Monitoring and Controlling LSF-HPC Jobs
All the standard LSF command s for monitoring a
job are supported. The bjobs command
reports the status of a job. The following is a
nexampleofthebjobs command.
$ bjobs
JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME
116 lsfadmi RUN normal lsfhost.loc 8*lsfhost.l * sleep 50 date time
12-8 LSF-HPC Administration