Options

-t [[month:]day:]hour:minute

Specifies the job termination deadline.

If a UNIX or Linux 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)).

In an application profile definition, a TERMINATE_CONTROL action can be configured to override the bkill default action (see the TERMINATE_CONTROL parameter in lsb.applications(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.

-Ureservation_ID If an advance reservation has been created with the brsvadd command, the -Uoption 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

The job can only use hosts reserved by the reservation user1#0. LSF only selects hosts in the reservation. You can use the -moption to specify particular hosts within the list of hosts reserved by the reservation, but you cannot specify other hosts not included in the original reservation.

If you do not specify hosts (bsub -m) or resource requirements (bsub -R), the default resource requirement is to select hosts that are of any host type (LSF assumes "type==any" instead of "type==local" as the default select string).

If you later delete the advance reservation while it is still active, any pending jobs still keep the "type==any" attribute.

A job can only use one reservation. There is no restriction on the number of jobs that can be submitted to a reservation; however, the number of slots available on the hosts in the reservation may run out. For example, reservation user2#0 reserves 128 slots on hostA. When all 128 slots on hostA are used by jobs referencing user2#0, hostA is no longer available to other jobs using reservation user2#0. Any single user or user group can have a maximum of 100 reservation IDs

Jobs referencing the reservation are killed when the reservation expires. LSF administrators can prevent running jobs from being killed when the reservation expires by changing the termination time of the job using the reservation (bmod -t) before the reservation window closes.

200Platform LSF Command Reference