Other changes to IBM Spectrum LSF
The following changes are related to command options and LSF default behavior.
Changed command options
Specify multiple email addresses with the bsub -u option
You can now specify multiple email addresses with the bsub -u option by enclosing the string in quotation marks and using a space to separate each email address. The total length of the address string cannot be longer than 511 characters.
The bpeek -f option now exits when the peeked job is complete
The bpeek -f command option now exits when the peeked job is completed.
If the peeked job is requeued or migrated, the bpeek command only exits if the job is completed again. In addition, the bpeek command cannot get the new output of the job. To avoid these issues, abort the previous bpeek -f command and rerun the bpeek -f command after the job is requeued or migrated.
Specify remote hosts with the bsub -m option
You can now specify remote hosts by using the bsub -m command option when using the job forwarding model with the LSF multicluster capability. To specify remote hosts, use host_name@cluster_name.
Changed configuration parameters
New MAX_PEND_SLOTS parameter and change to MAX_PEND_JOBS parameter
With the addition of the new parameter MAX_PEND_SLOTS, the concept of MAX_PEND_JOBS has changed. MAX_PEND_JOBS (in both lsb.users and lsb.params) has been changed to control the maximum pending "jobs" where previously it controlled the maximum pending "slot" threshold. MAX_PEND_SLOTS has been introduced therefore, to control the previous intention of MAX_PEND_JOBS.
This means that for customers who previously configured MAX_PEND_JOBS (for example, in lsb.users, for a user or group pending job slot limit), they must update the parameter to job count instead of slot count, or replace the parameter with the new MAX_PEND_SLOTS, which is meant for backward compatibility.
Changes to default LSF behavior
Improvements to the LSF Integration for Rational ClearCase
Daemon wrapper performance is improved with this release because the daemon wrappers no longer run the checkView function to check the ClearCase view (as set by the CLEARCASE_ROOT environment variable) under any conditions. In addition, the NOCHECKVIEW_POSTEXEC environment variable is now obsolete since it is no longer needed.
If the cleartool setview command fails when called by a daemon wrapper, the failure reason is shown in the bjobs -l, bhist -l, bstatus, and bread commands if DAEMON_WRAP_ENABLE_BPOST=Y is set as an environment variable.