Other changes to IBM Spectrum LSF 10.1 Fix Pack 6

Increased project name size

In previous versions of LSF, when submitting a job with a project name (by using the bsub -P option, the DEFAULT_PROJECT parameter in the lsb.params file, or by using the LSB_PROJECT_NAME or LSB_DEFAULTPROJECT environment variables), the maximum length of the project name was 59 characters. The maximum length of the project name is now increased to 511 characters.

This increase also applies to each project name that is specified in the PER_PROJECT and PROJECTS parameters in the lsb.resources file.

Cluster-wide DNS host cache

LSF can generate a cluster-wide DNS host cache file ($LSF_ENVDIR/.hosts.dnscache) that is used by all daemons on each host in the cluster to reduce the number of times that LSF daemons directly call the DNS server when starting the LSF cluster. To enable the cluster-wide DNS host cache file, configure LSF_DNS_CACHE=Y in the lsf.conf file.

Use #include for shared configuration file content

In previous versions of LSF, you can use the #INCLUDE directive to insert the contents of a specified file into the beginning of the lsf.shared or lsb.applications configuration files to share common configurations between clusters or hosts.

You can now use the #INCLUDE directive in any place in the following configuration files:

lsb.applications
lsb.hosts
lsb.queues
lsb.reasons
lsb.resources
lsb.users

You can use the #INCLUDE directive only at the beginning of the following file:

lsf.shared

For example, you can use #if … #endif Statements to specify a time-based configuration that uses different configurations for different times. You can change the configuration for the entire system by modifying the common file that is specified in the #INCLUDE directive.

Showing the pending reason for interactive jobs

The bsub -I command now displays the pending reason for interactive jobs, based on the setting of LSB_BJOBS_PENDREASON_LEVEL, if the job is pending.

Showing warning messages for interactive jobs

Interactive jobs can now show exit reasons when the jobs are killed (due to conditions such as reaching the memory or runtime limit). The exit reason is the same as the message shown for the output of the bhist -l and bjobs -l commands.

Changing job priorities and limits dynamically

Through the introduction of two new parameters, LSF now supports changing job priorities and limits dynamically through an import file. This includes:

Calling the eadmin script at a configured interval, even when a job exception has not occurred through the parameter EADMIN_TRIGGER_INTERVAL in the lsb.params file.
Allowing job submission during a policy update or cluster restart through the parameter PERSIST_LIVE_CONFIG in the lsb.params file.
Enhancement of the bconf command to override existing settings through the set action, to support the -pack option for reading multiple requests from a file.

Specify a UDP port range for LSF daemons

You can now specify a range of UDP ports to be used by LSF daemons. Previously, LSF binds to a random port number between 1024 and 65535.

To specify a UDP port range, define the LSF_UDP_PORT_RANGE parameter in the lsf.conf file. Include at least 10 ports in this range, and you can specify integers between 1024 and 65535.