LSF Version 7.3 - Using Platform LSF HPC

HP Vendor MPI Support
When you use mpirun in stand-alone mode, you specify host names to be used by the
MPI job.
Automatic HP MPI library configuration
During installation, lsfinstall sets LSF_VPLUGIN in lsf.conf to the full path
to the MPI library
libmpirm.sl. For example:
LSF_VPLUGIN="/opt/mpi/lib/pa1.1/libmpirm.sl"
On Linux hosts running HP MPI, you must manually set the full path to the HP vendor
MPI library
libmpirm.so.
For example, if HP MPI is installed in
/opt/hpmpi:
LSF_VPLUGIN="/opt/hpmpi/lib/linux_ia32/libmpirm.so"
The pam command
The pam command invokes the Platform Parallel Application Manager (PAM) to run
parallel batch jobs in LSF. It uses the HP
mpirun library to spawn the child processes
needed for the parallel tasks that make up your MPI application. It starts these tasks on
the systems allocated by LSF. The allocation includes the number of execution hosts
needed, and the number of child processes needed on each host.
Automatic host allocation by LSF
To achieve better resource utilization, you can have LSF manage the allocation of hosts,
coordinating the start-up phase with
mpirun.
This is done by preceding the regular HP MPI
mpirun command with:
bsub pam -mpi
The -mpi option on the bsub and pam command line is equivalent to mpirun in the
HP MPI environment. The
-mpi option must be the first option of the pam command.
Examples
For example, to run a single-host job and have LSF select the host, the command:
mpirun -np 14 a.out
is entered as:
bsub pam -mpi mpirun -np 14 a.out
For example, to run a multi-host job and have LSF select the hosts, the command:
mpirun -f appfile
is entered as:
bsub pam -mpi mpirun -f appfile
where appfile contains the following entries:
-h host1 -np 4 a.out
-h host2 -np 4 b.out
In this example, the hosts host1 and host2 are treated as symbolic names and refer to
the actual hosts that LSF allocates to the job.