LSF Version 7.3 - Using Platform LSF HPC

Other Integration Options
Once the PJL integration is successful, you might be interested in the following LSF
features.
For more information about these features, see the LSF documentation.
Using a job starter
A job starter is a wrapper script that can set up the environment before starting the
actual job.
Using external resources
You may need to identify MPI-enabled hosts
If all hosts in the LSF cluster can be used run the parallel jobs, with no restrictions, you
don’t need to differentiate between regular hosts and MPI-enabled hosts.
You can use an external resource to identify suitable hosts for running your parallel jobs.
To identify MPI-enabled hosts, you can configure a static Boolean resource in LSF.
For some integrations, to make sure the parallel jobs are sent to suitable hosts, you must
track a dynamic resource (such as free ports). You can use an LSF ELIM to report the
availability of these. See Administering Platform LSF for information about writing
ELIMs.
◆ If you create a dedicated LSF queue to manage the parallel jobs, make sure the
queue’s host list includes only MPI-enabled hosts.
◆ The bsub option -m host_name allows you to specify hosts by name. All the
hosts you name are used to run the parallel job.
◆ The bsub option -R res_req allows you to specify any LSF resource
requirements, including a list of hosts; in this case, you specify that the hosts selected
must have one of the names in your host list.
Using esub
An esub program can contain logic that modifies a job before submitting it to LSF. The
esub can be used to simplify the user input. An example is the LAM/MPI integration
in the Platform open source FTP directory.