1QRSUB(1)                   Grid Engine User Commands                  QRSUB(1)
2
3
4

NAME

6       qrsub   - Submit an Advance Reservation (AR) to Grid Engine.
7

SYNTAX

9       qrsub  [-a  date_time]  [-A account_string] [-ckpt ckpt_name] [-d time]
10       [-e date_time] [-he  yes|no]  [-help]  [-l  resource_list]  [-now]  [-M
11       user[@host],...]   [-N  ar_name]  [-w e|v] [-pe pe_name slot_range] [-q
12       wc_queue_list] [-u wc_user_list]
13

DESCRIPTION

15       Qrsub provides a means for operators, managers or users  referenced  in
16       the  ACL (see access_list(5)) "arusers" to create a Advance Reservation
17       (AR) in the Grid Engine queuing system. ARs allow to reserve particular
18       consumable  resources for future use. These reserved resources are only
19       available for jobs requesting the AR  and  the  scheduler  ensures  the
20       availability  of  the  resources  when  the  start time is reached. Job
21       requesting the AR can only use the reserved consumable resources.
22
23       During AR submit time the Grid Engine queuing system selects  the  best
24       suited  queues  for the AR request and then reserves the desired amount
25       of resources.  For a reservation, all queues that are not  in  orphaned
26       state  are  considered  as  suited.  Only if the AR request can be ful‐
27       filled, the AR will be granted.
28
29       ARs will be deleted either automatically when the end time is  reached,
30       or manually using qrdel .  In both cases, first all jobs requesting the
31       AR will be removed and then AR itself. Already granted ARs can be shown
32       with qrstat(.)
33
34       Note: To make AR behavior predictable, it is necessary to have reserved
35       resources available at the time of AR start. This is  done  by  keeping
36       jobs with a unlimited runtime limit separated from ARs, and not consid‐
37       ering resources used by such jobs for reservation.
38
39       Note: Resource Quotas are not considered for AR queue selection and nor
40       for jobs requesting a AR.
41
42       When  an  AR  was  successfully added to the Grid Engine queuing system
43       qrsub returns a unique integer ID referring the the newly  created  AR.
44       The  highest  AR  ID  is 9999999. If the highest ID is reached, a wrap‐
45       around happens and the next unused ID, starting with 1, will be used.
46
47       For qrsub, the administrator and the user may  define  default  request
48       files  (analogous  to  Grid Engine_request for qsub), which can contain
49       any of the possible command line options.
50       A cluster wide default request file is optional.   If  such  a  default
51       request file is used, it must be placed under
52       $GE_ROOT/$GE_CELL/common/sge_ar_request (global defaults file).
53       A user private default request file is optional. If it is used, it must
54       be placed under
55       $HOME/.sge_ar_request (user private defaults file).
56

OPTIONS

58       -a date_time
59              Defines the activation (start) date and  time  of  an  AR.   The
60              option  is  not  mandatory. If omitted, the current date_time is
61              assumed. Either a duration or end date_time must also be  speci‐
62              fied. For details about date_time please see sge_types(1)
63
64       -A account_string
65              Identifies  the account to which the resource reservation of the
66              AR should be charged. For "account_string" value details  please
67              see  the  "name"  definition in sge_types(1).  In the absence of
68              this parameter Grid Engine will place the default account string
69              "ge" in the accounting record of the AR.
70
71       -ckpt ckpt_name
72              Selects the checkpointing environment (see checkpoint(5)) the AR
73              jobs may request. Using this option guarantees queues that  only
74              providing this checkpoint environment will be reserved.
75
76       -d time
77              Defines the duration of the AR. The use of "-d time" is optional
78              if "-e date_time" is requested.  For details about  "time" defi‐
79              nition please see sge_types(1).
80
81       -e date_time
82              Defines  the  end  date  and  time  of  an  AR.  The  use of "-e
83              date_time" is optional if "-d time" is requested.   For  details
84              about "date_time" definition please see sge_types(1).
85
86       -he y[es]|n[o]
87              Specifies the behavior when the AR goes into an error state. The
88              AR goes into error state when a reserved host goes into  unknown
89              state,  a  queue  error  happens, or when a queue is disabled or
90              suspended.
91
92              A hard error, "-he yes", means as long as the  AR  is  in  error
93              state  no  jobs  using the AR will be scheduled.  If soft error,
94              "-he no", is specified the AR stays usable  with  the  remaining
95              resources.
96              By default soft error handling is used.
97
98
99       -help  Prints a list of all options.
100
101       -l resource=value,...
102              Creates  an  AR  in  a  Grid  Engine  queue, providing the given
103              resource request list.   complex(5)  describes  how  a  list  of
104              available  resources and their associated valid value specifiers
105              can be obtained.
106              There may be multiple -l switches in a single command.
107
108       -m b|e|a|n
109              Defines or redefines under which circumstances  mail  is  to  be
110              sent  to the AR owner or to the users defined with the -M option
111              described below. The option arguments have the  following  mean‐
112              ing:
113
114              `b'     Mail is sent at the beginning of the AR
115              `e'     Mail is sent at the end of the AR
116              `a'     Mail is sent when the AR goes into error state
117              `n'     No mail is sent, default for qrsub
118
119       -M user[@host],...
120              Defines  or  redefines  the  list  of users to which the qmaster
121              sends mail.
122
123       -masterq wc_queue_list
124              Only meaningful for a parallel AR request together with the  -pe
125              option.
126
127              This  option  is used to reserve the proper queues to match this
128              request if it would be requested by a  qsub.   A  more  detailed
129              description of wc_queue_list can be found in sge_types(1).
130
131       -now y[es]|n[o]
132              This options impacts the queues selection for reservation.
133              With  the  "-now y" option, only queues with the qtype "INTERAC‐
134              TIVE" assigned will be considered for reservation.  "-now n"  is
135              the default for qrsub.
136
137       -N name
138              The  name  of  the  AR.  The name, if requested, must conform to
139              "name" as defined in sge_types(1).  Invalid names will be denied
140              at submit time.
141
142       -w e|v Specifies the validation level applied to the AR request.
143
144              The specifiers e and v define the following validation modes:
145
146              `v'  verify - does not submit the AR but prints
147                   an extensive validation report
148              `e'  error - rejects request if requirements cannot
149                   be fulfilled, default for qrsub
150
151       -pe parallel_env n[-[m]]|[-]m,...
152              Parallel programming environment (PE) to select for the AR queue
153              reservation.  Please see the details of a PE in sge_pe(5).
154
155       -q wc_queue_list
156              Defines or redefines a list of cluster queues, queue domains  or
157              queue  instances,  that may be reserved by the AR. Please find a
158              description of wc_queue_list in  sge_types(1).   This  parameter
159              has  all the properties of a resource request and will be merged
160              with requirements derived from the -l option described above.
161
162       -u [username|@access_list],...
163              Defines the users allowed to submit jobs requesting the AR.  The
164              access  is  specified  by a comma separated list containing UNIX
165              users or ACLs (see access_list(5)).  prefixing the ACL name with
166              an '@' sign.
167              By  default only the AR owner is allowed to submit jobs request‐
168              ing the AR.
169
170              Note: Only queues, where all users specified in  the  list  have
171              access, are considered for reservation (see queue_conf(5)).
172

ENVIRONMENTAL VARIABLES

174       GE_ROOT        Specifies  the location of the Grid Engine standard con‐
175                      figuration files.
176
177       GE_CELL        If set, specifies  the  default  Grid  Engine  cell.  To
178                      address  a Grid Engine cell, qsub, qsh, qlogin or qalter
179                      use (in the order of precedence):
180
181                             The name of the cell specified in the environment
182                             variable GE_CELL, if it is set.
183
184                             The name of the default cell, i.e. default.
185
186       GE_DEBUG_LEVEL If set, specifies that debug information should be writ‐
187                      ten to stderr. In addition the level of detail in  which
188                      debug information is generated is defined.
189
190       GE_QMASTER_PORT
191                      If set, specifies the TCP port on which ge_qmaster(8) is
192                      expected to listen  for  communication  requests.   Most
193                      installations will use a services map entry for the ser‐
194                      vice "sge_qmaster" instead of defining the port.
195

FILES

197       $GE_ROOT/$GE_CELL/common/sge_ar_request
198                     global defaults file
199       $HOME/.sge_ar_request
200                     user private defaults file
201

SEE ALSO

203       qrdel(1), qrstat(1), qsub(1), sge_types(1), checkpoint(5),  complex(5),
204       queue_conf(5), sge_pe(5), sge_resource_quota(5).
205
207       See ge_intro(1) for a full statement of rights and permissions.
208
209
210
211
212GE 6.2u5                 $Date: 2008/05/21 09:47:34 $                 QRSUB(1)
Impressum