This maximum path length includes the temporary directories and files that the LSF system creates as jobs run.
The path you specify for JOB_SPOOL_DIR should be as short as possible to avoid exceeding this limit.
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.
command and do not get up-to-date information, you may need to decrease the value of this parameter.
Like LSB_SHAREDIR, the directory should be owned and writable by the primary LSF administrator.
This maximum path length includes the temporary directories and files that LSF Batch creates as jobs run.If you are not concerned with the interference with interactive jobs caused by paging, the value of this parameter may be set to 0. Enables license preemption when preemptive scheduling is enabled (has no effect if PREEMPTIVE is not also specified) and specifies the licenses that will be preemption resources.Specify shared numeric resources, static or decreasing, that LSF is configured to release (RELEASE=Y in The update is done only if the value for the CPU time, resident memory usage, or virtual memory usage has changed by more than 10 percent from the previous update or if a new process or process group has been created.Date Modified: June 29, 2000 Platform Computing Corporation: America: 1 9 Europe: 44 1256 370 530 Asia: 86 1062 381125 Toll-Free: 1-877-444-4LSF ( 1 8) LSF Support: [email protected] Documentation: [email protected] © 2000 Platform Computing Corporation All rights reserved.If the specified directory is not accessible or does not exist, JOB_SPOOL_DIR can be any valid path up to a maximum length of 256 characters.The CPU factor of the specified host or host model will be used to normalize the CPU time limit of all jobs in the cluster, unless the CPU time normalization host is specified at the queue or job level.When you submit a job to LSF without explicitly specifying a queue, and the environment variable LSB_DEFAULTQUEUE is not set, LSF puts the job in the first queue in this list that satisfies the job's specifications subject to other restrictions, such as requested hosts, queue status, etc. When a user submits a job to LSF without explicitly specifying a queue, and there are no candidate default queues defined (by this parameter or by the user's environment variable LSB_DEFAULTQUEUE), LSF automatically creates a new queue named To calculate dynamic user priority, LSF scales the actual CPU time using a decay factor, so that 1 hour of recently-used time is equivalent to 0.1 hours after the specified number of hours has elapsed., JOB_SPOOL_DIR must be readable and writable by the job submission user, and it must be shared by the master host and the submission host.If the specified directory is not accessible or does not exist, and JOB_SPOOL_DIR is specified, JOB_SPOOL_DIR can be any valid path up to a maximum length of 256 characters.When HIST_HOURS=0 is specified, the history CPU time is not considered.If 0 (zero), a host may accept more than one job in each job dispatching interval.