LSF Version 7.3 - Using Platform LSF HPC

Using the pam -n option (SGI MPI only)
The -n option on the pam command line specifies the number of tasks that PAM should
start.
You can use both
bsub -n and pam -n in the same job submission. The number
specified in the
pam -n option should be less than or equal to the number specified by
bsub -n. If the number of task specified with pam -n is greater than the number
specified by
bsub -n, the pam -n is ignored.
For example, you can specify:
bsub -n 5 pam -n 2 -mpi a.out
Here, 5 processors are reserved for the job, but PAM only starts 2 parallel tasks.
Custom job controls for parallel jobs
As with sequential LSF jobs, you can use the JOB_CONTROLS parameter in the queue
(
lsb.queues) to configure custom job controls for your parallel jobs.
How to use these two variables in your job control scripts:
◆ If pam and the job RES are in same process group, use LSB_JOBRES_PID. Here
is an example of JOB_CONTROL defined in the queue:
A signal name (for example, SIGSTOP or
SIGTSTP)
Propagates the signal to the PAM PGID and all
parallel tasks
A
/bin/sh command line or script Sets all job environment variables for the
command action.
Sets the following additional environment
variables:
◆ LSB_JOBPGIDS—a list of current process
group IDs of the job
◆ LSB_JOBPIDS—a list of current process
IDs of the job
◆ LSB_PAMPID — the PAM process ID
◆ LSB_JOBRES_PID—the process ID of
RES for the job
For the SUSPEND action command, sets the
following environment variables:
◆ LSB_SUSP_REASONS—an integer
representing a bitmap of suspending reasons
as defined in lsbatch.h. The suspending
reason can allow the command to take
different actions based on the reason for
suspending the job.
◆ LSB_SUSP_SUBREASONS—an integer
representing the load index that caused the
job to be suspended. When the suspending
reason SUSP_LOAD_REASON
(suspended by load) is set in
LSB_SUSP_REASONS,
LSB_SUSP_SUBREASONS set to one of
the load index values defined in lsf.h.