Platform LSF Reference Version 6.2

bsub
Platform LSF Reference
167
-sp priority
Specifies user-assigned job priority which allow users to order their jobs in a queue. Valid
values for priority are any integers between 1 and MAX_USER_PRIORITY (displayed
by
bparams -l). Job priorities that are not valid are rejected. LSF and queue
administrators can specify priorities beyond MAX_USER_PRIORITY.
The job owner can change the priority of their own jobs. LSF and queue administrators
can change the priority of all jobs in a queue.
Job order is the first consideration to determine job eligibility for dispatch. Jobs are still
subject to all scheduling policies regardless of job priority. Jobs with the same priority
are ordered first come first served.
User-assigned job priority can be configured with automatic job priority escalation to
automatically increase the priority of jobs that have been pending for a specified period
of time.
-t [[month:]day:]hour:minute
Specifies the job termination deadline.
If a UNIX job is still running at the termination time, the job is sent a SIGUSR2 signal,
and is killed if it does not terminate within ten minutes.
If a Windows job is still running at the termination time, it is killed immediately. (For a
detailed description of how these jobs are killed, see
bkill.)
In the queue definition, a TERMINATE action can be configured to override the
bkill default action (see the JOB_CONTROLS parameter in lsb.queues(5)).
The format for the termination time is [[month:]day:]hour:minute where the number ranges
are as follows: month 1-12, day 1-31, hour 0-23, minute 0-59.
At least two fields must be specified. These fields are assumed to be hour:minute. If three
fields are given, they are assumed to be day:hour:minute, and four fields are assumed to be
month:day:hour:minute.
-T thread_limit
Sets the limit of the number of concurrent threads to thread_limit for the whole job. The
default is no limit.
Exceeding the limit causes the job to terminate. The system sends the following signals
in sequence to all processes belongs to the job: SIGINT, SIGTERM, and SIGKILL.
-U reservation_ID
If an advance reservation has been created with the brsvadd command, the -U option
makes use of the reservation.
For example, if the following command was used to create the reservation user1#0,
% brsvadd -n 1024 -m hostA -u user1 -b 13:0 -e 18:0
Reservation "user1#0" is created
The following command uses the reservation:
%bsub -U user1#0 myjob