Platform LSF Reference Version 6.2

Parameters Section
Platform LSF Reference
386
LSF assigns job IDs in sequence. When the job ID limit is reached, the count rolls over,
so the next job submitted gets job ID "1". If the original job 1 remains in the system,
LSF skips that number and assigns job ID "2", or the next available job ID. If you have
so many jobs in the system that the low job IDs are still in use when the maximum job
ID is assigned, jobs with sequential numbers could have totally different submission
times.
By raising the job ID limit, you allow more time for old jobs to leave the system, and
make it more likely that numbers can be assigned in sequence without conflicting with
existing jobs.
Example
MAX_JOBID=1234567
Default
999999
MAX_JOBINFO_QUERY_PERIOD
Syntax MAX_JOBINFO_QUERY_PERIOD=integer
Description
Maximum time for job information query commands (for example, with bjobs) to
wait.
When the time arrives, the query command processes exit, and all associated threads are
terminated.
If the parameter is not defined, query command processes will wait for all threads to
finish.
Specify a multiple of MBD_REFRESH_TIME.
Valid values
Any positive integer greater than or equal to one (1)
Default
Undefined
See also
See “lsf.conf” under “LSB_BLOCK_JOBINFO_TIMEOUT” on page 509.
MAX_JOB_MSG_NUM
Syntax
MAX_JOB_MSG_NUM=
integer | 0
Description
Maximum number of message slots for each job. Maximum number of messages that
can be posted to a job with the
bpost(1) command.
0 indicates that jobs cannot accept external messages.
Default
128
MAX_JOB_NUM
Syntax
MAX_JOB_NUM=
integer
Description
The maximum number of finished jobs whose events are to be stored in the
lsb.events log file.
Once the limit is reached,
mbatchd starts a new event log file. The old event log file is
saved as
lsb.events.n, with subsequent sequence number suffixes incremented by 1
each time a new log file is started. Event logging continues in the new
lsb.events file.
Default
1000