Platform LSF Administration Guide Version 6.2

Using Advance Reservation
Administering Platform LSF
368
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.
Modifying jobs
(bmod -U)
Administrators can use the -U option of bmod to change a job to another reservation
ID. For example:
% bmod -U user1#0 1234
To cancel the reservation, use the
-Un option of bmod. For example:
% bmod -Un 1234
Changing job termination time (bmod -t)
Before the reservation window closes, administrators can use the -t option of bmod to
change the termination time of a running job that is using the reservation. This prevents
the job from being killed when the reservation expires; it does not extend the actual
reservation window. For example:
% bmod -t 15:0 1234
You must set LSB_MOD_ALL_JOBS=Y in lsf.conf to use bmod -t for advance
reservations.
LSF users and administrators can modify the termination time of an open advance
reservation without interfering with current job scheduling policies. If the new
termination time of the advance reservation window overlaps with other open advance
reservations, the job will suspend at the time of the overlap. When all open advance
reservations are closed, running jobs using the reservations will also suspend, and
current scheduling policies will take effect for these jobs. For example, you specify two
open advance reservations as follows:
% brsvadd -o -n 1 -m hostA -u user1 -b 15:10 -e 15:30
Reservation user1#17 is created
% brsvadd -o -n 1 -m hostA -u user1 -b 15:35 -e 15:50
Reservation user1#18 is created
At 15:15, while job 122 in user1#17 is running, you modify its termination time as
follows:
% bmod -t 15:40 122
This termination time overlaps the reservation window of user1#18, in which job 245
started at 15:35. After modifying the termination time of job 122, the following events
occur:
At this time ... These events occur ...
15:35
◆ Job 122 in reservation user1#17 suspends
◆ Job 245 in reservation user1#18 starts
15:40
◆ Job 122 in reservation user#17 is still suspended
◆ Job 245 in reservation user#18 continues to run
15:50
◆ Job 122 in reservation user1#17 suspends
◆ Job 245 in reservation user1#18 suspends
15:51
◆ Job 122 in reservation user1#17 runs
◆ Job 245 in reservation user1#18 suspends