Command Reference Guide

Options
160 Platform LSF Command Reference
You must sp e ci f y at le ast hour:minute. Year, month, and day are optional. Three
fields are assumed to be day
:hour:minute, four fields are assumed to be
month
:day:hour:minute, and five fields are year:month:day:hour:minute.
If you do not specify a day, LSF assumes the current day. If you do not specify a
month, LSF assumes the current month. If you specify a year, you must specify a
month.
The offset is in minutes, an integer with a prefix
+ or -. For example, -b+5 moves the
begin time 5 minutes later, and
-b-5 moves the begin time 5 minutes earlier.
The modified time value for
-b must use the same syntax as the time value for -e.
It must be earlier than the time value for
-e, and cannot be earlier than the current
time.
-d "description" Replaces or sets a description for the reservation. The description must be provided
as a double quoted text string. The maximum length is 512 characters.
-e end_time | [+ | -]minutes
Replaces the end time for a one-time reservation, or gives an offset in minutes to
the current end time.
By giving a positive offset to the end time, you extend the duration of a reservation
so that the jobs in the reservation can run longer. Shrinking the reservation with a
negative value terminates running jobs earlier.
The end time is in the form
[[[year:]month:]day:]hour:minute
with the following ranges:
year: any year after 1900 (YYYY)
month: 1-12 (MM)
day of the month: 1-31 (dd)
hour: 0-23 (hh)
minute: 0-59 (mm)
You must sp e ci f y at le ast hour
:minute. Year, month, and day are optional. Three
fields are assumed to be day
:hour:minute, four fields are assumed to be
month
:day:hour:minute, and five fields are year:month:day:hour:minute.
If you do not specify a day, LSF assumes the current day. If you do not specify a
month, LSF assumes the current month. If you specify a year, you must specify a
month.
The time value for
-e must use the same syntax as the time value for -b. It must be
later than the time value for
-b.
-g group_name Changes the user group that is able to submit jobs to the reservation. Changing the
user group does not affect the currently running jobs.
Jobs submitted by the original user group to the reservation still belong to the
reservation and scheduled as advance reservation jobs, but newly submitted jobs
from a user group that has been removed from the reservation cannot use the
reservation any longer.
The
-g group_name option does not support the @cluster notation for advance
reservations on remote clusters.