Task startup for LSF HPC generic PJL jobs
For parallel jobs submitted with bsub:
◆PAM invokes the PJL, which in turn invokes the TaskStarter (TS).
◆TS starts the tasks on each execution host, reports the process ID to PAM, and waits for the task to finish.
Options
Options for vendor MPI jobs
-auto_placeThe -auto_placeoption on the pam command line tells the SGI IRIX mpirun library to launch the MPI application according to the resources allocated by LSF.
-mpiIn the SGI environment, the -mpioption on the bsub and pam command line is equivalent to the mpirun command.
On HP-UX, you can have LSF manage the allocation of hosts to achieve better resource utilization by coordinating the start-up phase with mpirun. This is done by preceding the regular HP MPI mpirun command with:
bsub pam -mpi
For HP-UX vendor MPI jobs, the -mpioption must be the first option of the pam command.
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
-nnum_tasks The number of processors required to run the MPI application, typically the number of parallel tasks in the job. If the host is a multiprocessor, one host can start several tasks.
You can use both bsub -n and pam -nin the same job submission. The number specified in the pam -noption should be less than or equal to the number specified by bsub -n. If the number of tasks specified with pam -nis greater than the number specified by bsub -n, the pam -nis ignored.
For example, on SGI IRIX or SGI Altix, you can specify:
bsub -n 5 pam -n 2 -mpi -auto_place a.out
Here, the job requests 5 processors, but PAM only starts 2 parallel tasks.
mpi_app [argument ...]
The name of the MPI application to be run on the listed hosts. This must be the last argument on the command line.
-hPrints command usage to stderr and exit.
-VPrints LSF release version to stderr and exit.