pbs_rsub.1B 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694
  1. .\" Copyright (C) 1994-2018 Altair Engineering, Inc.
  2. .\" For more information, contact Altair at www.altair.com.
  3. .\"
  4. .\" This file is part of the PBS Professional ("PBS Pro") software.
  5. .\"
  6. .\" Open Source License Information:
  7. .\"
  8. .\" PBS Pro is free software. You can redistribute it and/or modify it under the
  9. .\" terms of the GNU Affero General Public License as published by the Free
  10. .\" Software Foundation, either version 3 of the License, or (at your option) any
  11. .\" later version.
  12. .\"
  13. .\" PBS Pro is distributed in the hope that it will be useful, but WITHOUT ANY
  14. .\" WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
  15. .\" FOR A PARTICULAR PURPOSE.
  16. .\" See the GNU Affero General Public License for more details.
  17. .\"
  18. .\" You should have received a copy of the GNU Affero General Public License
  19. .\" along with this program. If not, see <http://www.gnu.org/licenses/>.
  20. .\"
  21. .\" Commercial License Information:
  22. .\"
  23. .\" For a copy of the commercial license terms and conditions,
  24. .\" go to: (http://www.pbspro.com/UserArea/agreement.html)
  25. .\" or contact the Altair Legal Department.
  26. .\"
  27. .\" Altair’s dual-license business model allows companies, individuals, and
  28. .\" organizations to create proprietary derivative works of PBS Pro and
  29. .\" distribute them - whether embedded or bundled with other software -
  30. .\" under a commercial license agreement.
  31. .\"
  32. .\" Use of Altair’s trademarks, including but not limited to "PBS™",
  33. .\" "PBS Professional®", and "PBS Pro™" and Altair’s logos is subject to Altair's
  34. .\" trademark licensing policies.
  35. .\"
  36. .TH pbs_rsub 1B "19 February 2018" Local "PBS Professional"
  37. .SH NAME
  38. .B pbs_rsub
  39. \- create a PBS advance or standing reservation
  40. .SH SYNOPSIS
  41. .B pbs_rsub
  42. [-D <duration>] [-E <end time>] [-g <group list>]
  43. .RS 9
  44. [-G <auth group list>] [-H <auth host list>] [-I <block time>]
  45. [-m <mail events>] [-M <mail list>] [-N <reservation name>]
  46. [-q <destination>] [-r <recurrence rule>] [-R <start time>]
  47. [-u <user list>] [-U <auth user list>] [-W <attribute value list>]
  48. -l <resource request> [-l <placement>]
  49. .RE
  50. .B pbs_rsub
  51. --version
  52. .SH DESCRIPTION
  53. The
  54. .B pbs_rsub
  55. command is used to create an advance or standing reservation.
  56. An advance reservation reserves specific
  57. resources for the requested time period, and a standing reservation
  58. reserves specific resources for recurring time periods. When
  59. a reservation is created, it has an associated queue.
  60. After the reservation is requested, it is either confirmed or denied.
  61. Once the reservation has been confirmed, authorized users submit jobs to the
  62. reservation's queue via
  63. .B qsub
  64. and
  65. .B qmove.
  66. A confirmed reservation will accept jobs at any time.
  67. The jobs in its queue can run only during the reservation
  68. period, whether during a single advance reservation or
  69. during the occurrences of a standing reservation.
  70. When an advance reservation ends, all of its jobs are
  71. deleted, whether running or queued. When an occurrence of a
  72. standing reservation ends, only its running jobs are deleted;
  73. those jobs still in the queue are not deleted.
  74. To get information about a reservation, use the
  75. .B pbs_rstat
  76. command.
  77. To delete a reservation, use the
  78. .B pbs_rdel
  79. command. Do not use the
  80. .B qdel
  81. command.
  82. The behavior of the
  83. .B pbs_rsub
  84. command may be affected by
  85. any site hooks. Site hooks can modify the reservation's attributes.
  86. .SH REQUIREMENTS
  87. When using
  88. .B pbs_rsub
  89. to request a reservation, you must specify two of the following
  90. options:
  91. .I -R, -E,
  92. and
  93. .I -D.
  94. The resource request
  95. .I -l walltime
  96. can be used instead of the
  97. .I -D
  98. option.
  99. If you want to run jobs in a reservation that will request exclusive placement,
  100. you must create the reservation with exclusive placement via -l place=excl.
  101. .SH OPTIONS
  102. .IP "-D <duration>" 8
  103. Specifies reservation duration. If the start
  104. time and end time are the only times specified, this duration time is
  105. calculated.
  106. .br
  107. Format:
  108. .I Duration.
  109. See
  110. .B FORMATS.
  111. .br
  112. Default: none
  113. .RE
  114. .IP "-E <end time>" 8
  115. Specifies the reservation end time. If start time and duration are
  116. the only times specified, the end time value is calculated.
  117. .br
  118. Format:
  119. .I Datetime.
  120. See
  121. .B FORMATS.
  122. .br
  123. Default: none.
  124. .RE
  125. .IP "-g <group list>" 8
  126. The
  127. .I group list
  128. is a comma-separated list of group names.
  129. The server uses entries in this list, along with an ordered set
  130. of rules, to associate a group name with the reservation.
  131. The reservation creator's primary group is automatically added to this list.
  132. .br
  133. Format: <group>@<hostname>[,<group>@<hostname> ...]
  134. .RE
  135. .IP "-G <auth group list>" 8
  136. Comma-separated list of names of groups who
  137. can or cannot submit jobs to this reservation. Group names are
  138. interpreted in the context of the server's host, not the context of the host
  139. from which the job is submitted.
  140. .br
  141. This list becomes the
  142. .I acl_groups
  143. list for the
  144. reservation's queue.
  145. More specific entries should be listed before more general, because the
  146. list is read left-to-right, and the first match determines access.
  147. .br
  148. If both the
  149. .I Authorized_Users
  150. and
  151. .I Authorized_Groups
  152. reservation attributes are set, a user must belong to both in order to
  153. be able to submit jobs to this reservation. If the reservation
  154. creator specifies this list, the creator's group is not automatically
  155. added to the list.
  156. .br
  157. Refer to the
  158. .I Authorized_Groups
  159. reservation attribute in the
  160. pbs_resv_attributes(7B) man page.
  161. .br
  162. Format: [+|-]<group name>[,[+|-]<group name> ...]
  163. .br
  164. Default: All groups are authorized to submit jobs.
  165. .RE
  166. .IP "-H <auth host list>" 8
  167. Comma-separated list of hosts from which jobs can and cannot be
  168. submitted to this reservation. This list becomes the
  169. .I acl_hosts
  170. list for the reservation's queue.
  171. .br
  172. More specific entries should be listed before more general, because the
  173. list is read left-to-right, and the first match determines access.
  174. If the reservation creator specifies this list, the creator's
  175. host is not automatically added to the list.
  176. .br
  177. See the
  178. .I Authorized_Hosts
  179. reservation attribute in the pbs_resv_attributes(7B) man page.
  180. .br
  181. Format: [+|-]<hostname>[,[+|-]<hostname> ...]
  182. .br
  183. Default: All hosts are authorized to submit jobs
  184. .RE
  185. .IP "-I <block time>" 8
  186. Specifies interactive mode. The
  187. .B pbs_rsub
  188. command will block, up to
  189. .I block time
  190. seconds, while waiting for the reservation request to be
  191. confirmed or denied.
  192. .br
  193. If
  194. .I block time
  195. is positive, and the reservation isn't confirmed or denied in
  196. the specified time, the ID string for the reservation is returned
  197. with the status "UNCONFIRMED".
  198. .br
  199. If
  200. .I block time
  201. is negative, and a scheduler doesn't confirm or deny the reservation in
  202. the specified time, the reservation is deleted.
  203. .br
  204. Format: Integer.
  205. .br
  206. Default: Not interactive
  207. .RE
  208. .IP "-l <placement>" 8
  209. The
  210. .I placement
  211. specifies how vnodes are reserved.
  212. The
  213. .I place
  214. statement can contain the following elements, in any order:
  215. .IP " " 11
  216. -l place=[
  217. .I <arrangement>
  218. ][:
  219. .I <sharing>
  220. ][:
  221. .I <grouping>
  222. ]
  223. .LP
  224. .IP " " 8
  225. where
  226. .IP " " 11
  227. .RS
  228. .IP arrangement 3
  229. Whether this reservation chunk is willing to share this vnode or host
  230. with other chunks from this reservation. One of
  231. .I free
  232. |
  233. .I pack
  234. |
  235. .I scatter
  236. |
  237. .I vscatter
  238. .IP sharing 3
  239. Whether this reservation chunk is willing to share this vnode or host
  240. with other reservations or jobs. One of
  241. .I excl
  242. |
  243. .I share
  244. |
  245. .I exclhost
  246. .IP grouping 3
  247. Whether the chunks from this reservation should be placed on vnodes
  248. that all have the smae value for a resource. Can have only one
  249. instance of
  250. .I group=resource
  251. .LP
  252. .LP
  253. .RE
  254. .LP
  255. .IP " " 8
  256. and where
  257. .IP " " 11
  258. .RS
  259. .IP free 3
  260. Place reservation on any vnode(s).
  261. .IP pack
  262. All chunks are taken from one host.
  263. .IP scatter 3
  264. Only one chunk with any MPI processes is taken from a host.
  265. A chunk with no MPI processes may be taken from the same vnode as
  266. another chunk.
  267. .IP vscatter 3
  268. Only one chunk is taken from any vnode. Each chunk must fit on a vnode.
  269. .IP excl 3
  270. Only this reservation uses the vnodes chosen.
  271. .IP exclhost 3
  272. The entire host is allocated to the reservation.
  273. .IP shared 3
  274. This reservation can share the vnodes chosen.
  275. .IP group=<resource> 3
  276. Chunks are grouped according to a
  277. .I resource.
  278. All vnodes in the group must have a common value for
  279. .I resource,
  280. which can be either the built-in resource
  281. .I host
  282. or a custom vnode-level resource.
  283. .br
  284. .I resource
  285. must be a string or a string array.
  286. .LP
  287. .LP
  288. .RE
  289. .LP
  290. .IP " " 8
  291. If you want to run jobs in the reservation that will request exclusive
  292. placement, you must create the reservation with exclusive placement via
  293. .B -l place=excl.
  294. The place statement cannot begin with a colon. Colons are delimiters; use
  295. them only to separate parts of a place statement, unless they are quoted
  296. inside resource values.
  297. Note that nodes can have sharing attributes that override
  298. job placement requests. See the
  299. .B pbs_node_attributes(7B)
  300. man page.
  301. .LP
  302. .IP " " 8
  303. For more on reservations, see
  304. .B The PBS Professional User's Guide.
  305. .RE
  306. .IP "-l resource request" 8
  307. The
  308. .I resource request
  309. specifies the resources required for the reservation. These
  310. resources are used for the limits on the queue that is dynamically created
  311. for the reservation. The aggregate amount of resources for currently
  312. running jobs from this queue will not exceed these resource limits.
  313. Jobs in the queue that
  314. request more of a resource than the queue limit for that resource are not
  315. allowed to run. Also, the queue inherits the value of any resource limit set
  316. on the server, and these are used for the job if the reservation request
  317. itself is silent about that resource.
  318. A non-privileged user cannot submit a reservation requesting a custom
  319. resource which has
  320. been created to be invisible or read-only for users.
  321. Resources are requested
  322. by using the
  323. .I -l
  324. option, either in
  325. .I chunks
  326. inside of
  327. .I selection statements,
  328. or in job-wide requests using
  329. .I <resource name>=<value>
  330. pairs.
  331. Requesting resources in chunks:
  332. .RS
  333. .IP " " 3
  334. .I -l select=[N:]<chunk>[+[N:]<chunk> ...]
  335. .LP
  336. where
  337. .I N
  338. specifies how many of that chunk, and
  339. a
  340. .I chunk
  341. is of the form:
  342. .IP " " 3
  343. .I <resource name>=<value>[:<resource name>=<value> ...]
  344. .LP
  345. Requesting job-wide resources:
  346. .IP " " 3
  347. .I -l <resource name>=<value>[,<resource name>=<value> ...]
  348. .LP
  349. .RE
  350. .IP "-m <mail events>" 8
  351. Specifies the set of events that cause mail to be sent to the
  352. list of users specified in the
  353. .I -M mail list
  354. option.
  355. .br
  356. Format: string consisting of one of the following:
  357. .RS
  358. 1) any combination of "a", "b", "c" or "e"
  359. .br
  360. 2) the single character "n"
  361. .IP a
  362. Notify if the reservation is terminated for whatever reason
  363. .IP b
  364. Notify when the reservation period begins
  365. .IP c
  366. Notify when the reservation is confirmed
  367. .IP e
  368. Notify when the reservation period ends
  369. .IP n
  370. Send no mail. Cannot be used with any of
  371. .I a, b, c
  372. or
  373. .I e.
  374. .LP
  375. Default:
  376. .I ac
  377. .RE
  378. .IP "-M <mail list>" 8
  379. The list of users to whom mail is sent
  380. whenever the reservation transitions to one of the states
  381. specified in the
  382. .I -m mail events
  383. option.
  384. .br
  385. Format: <username>[@<hostname>][,<username>[@<hostname>]...]
  386. .br
  387. Default: reservation owner.
  388. .RE
  389. .IP "-N <reservation name>" 8
  390. Specifies a name for the reservation.
  391. .br
  392. Format:
  393. .I Reservation name.
  394. See
  395. .B FORMATS.
  396. .br
  397. Default: None.
  398. .RE
  399. .IP "-q <destination>" 8
  400. Specifies the destination server at which to create the reservation.
  401. .br
  402. Default: The default server is used if this option is not selected.
  403. .RE
  404. .IP "-r <recurrence rule>" 8
  405. Specifies rule for recurrence of standing reservations. Rule must conform to iCalendar
  406. syntax, and is specified using a subset of parameters from RFC 2445.
  407. .br
  408. Valid syntax for
  409. .I recurrence rule
  410. takes one of two forms:
  411. .RS 11
  412. .I FREQ=<freq spec>;COUNT=<count spec>;<interval spec>
  413. .RE
  414. .IP " " 8
  415. or
  416. .RS 11
  417. .I FREQ=<freq spec>;UNTIL=<until spec>; <interval spec>
  418. .RE
  419. .IP " " 8
  420. where
  421. .RS 11
  422. .IP "freq spec" 5
  423. Frequency with which the standing reservation repeats. Valid values are:
  424. .br
  425. WEEKLY|DAILY|HOURLY
  426. .IP "count spec" 5
  427. The exact number of occurrences. Number up to 4 digits in length.
  428. Format: integer.
  429. .IP "interval spec" 5
  430. Specifies interval. Format is one or both of:
  431. .br
  432. BYDAY = MO|TU|WE|TH|FR|SA|SU
  433. .br
  434. or
  435. .br
  436. BYHOUR = 0|1|2|...|23
  437. .br
  438. When using both, separate them with a semicolon.
  439. .br
  440. Elements specified in the recurrence rule override those
  441. specified in the arguments to the
  442. .I -R
  443. and
  444. .I -E
  445. options. For example, the
  446. .I BYHOUR
  447. specification overrides the hourly part of the
  448. .I -R
  449. option. For example,
  450. .br
  451. -R 0730 -E 0830 ... BYHOUR=9
  452. .br
  453. results in a reservation that starts at 9:30 and runs for 1 hour.
  454. See the
  455. .B PBS Professional User's Guide.
  456. .IP "until spec" 5
  457. Occurrences will start up to but not after date and time
  458. specified.
  459. .br
  460. Format: YYYYMMDD[THHMMSS]
  461. .br
  462. Note that the year-month-day section is separated from
  463. the hour-minute-second section by a capital T.
  464. .RE
  465. .IP " " 8
  466. Requirements:
  467. .br
  468. The recurrence rule must be on one unbroken line and must be enclosed
  469. in double quotes.
  470. A start and end date must be used when specifying a recurrence rule.
  471. See the
  472. .I R
  473. and
  474. .I E
  475. options.
  476. The PBS_TZID environment variable must be set at the submission host. The
  477. format for PBS_TZID is a timezone location. Examples: America/Los_Angeles,
  478. America/Detroit, Europe/Berlin, Asia/Calcutta. See the
  479. .B PBS Professional User's Guide.
  480. .B Examples of Standing Reservations
  481. .br
  482. For a reservation that runs every day from 8am to 10am, for a total of 10 occurrences:
  483. .RS
  484. .IP " " 3
  485. pbs_rsub -R 0800 -E 1000 -r "FREQ=DAILY;COUNT=10"
  486. .LP
  487. Every weekday from 6am to 6pm until December 10 2008
  488. .IP " " 3
  489. pbs_rsub -R 0600 -E 1800
  490. .br
  491. -r "FREQ=WEEKLY; BYDAY=MO,TU,WE,TH,FR; UNTIL=20081210"
  492. .LP
  493. Every week from 3pm to 5pm on Monday, Wednesday, and Friday, for 9 occurrences,
  494. i.e., for three weeks:
  495. .RS 5
  496. pbs_rsub -R 1500 -E 1700
  497. .br
  498. -r "FREQ=WEEKLY;BYDAY=MO,WE,FR; COUNT=3"
  499. .RE
  500. .RE
  501. .IP "-R <start time>" 8
  502. .RS
  503. .LP
  504. Specifies reservation starting time. If the reservation's end time
  505. and duration are the only times specified, this start time is calculated.
  506. If the day,
  507. .I DD ,
  508. is not specified, it defaults to today if the time
  509. .I hhmm
  510. is in the future. Otherwise, the day is set to tomorrow.
  511. For example, if you submit a reservation with the specification
  512. .I "-R 1110"
  513. at 11:15 a.m., it is interpreted as being for 11:10am tomorrow.
  514. If the month portion,
  515. .I MM ,
  516. is not specified, it defaults to the current month, provided that the specified
  517. day
  518. .I DD ,
  519. is in the future. Otherwise, the month is set to next month. Similar
  520. rules apply to the two other optional, left-side components.
  521. .br
  522. Format:
  523. .I Datetime
  524. .LP
  525. .RE
  526. .IP "-u <user list>" 8
  527. Not used. Comma-separated list of user names.
  528. .br
  529. Format: <username>[@<hostname>][,<username>[@<hostname>] ...]
  530. .br
  531. Default: None
  532. .RE
  533. .IP "-U <auth user list>" 8
  534. Comma-separated list of users who are and are not allowed to
  535. submit jobs to this reservation.
  536. This list becomes the
  537. .I acl_users
  538. attribute for the reservation's queue.
  539. More specific entries should be listed before more general, because the
  540. list is read left-to-right, and the first match determines access.
  541. If both the
  542. .I Authorized_Users
  543. and
  544. .I Authorized_Groups
  545. reservation attributes are set, a user must belong to both in order to be able to
  546. submit jobs to this reservation.
  547. The reservation creator's username is automatically added to this list,
  548. whether or not the reservation creator specifies this list.
  549. Refer to the
  550. .I Authorized_Users
  551. reservation attribute on the pbs_resv_attributes man page.
  552. .br
  553. Format:
  554. .I [+|-]<username>@<hostname>[,[+|-]<username>@<hostname>...]
  555. .br
  556. Default: Job owner only
  557. .br
  558. .RE
  559. .IP "-W attribute value list" 8
  560. This allows you to define other attributes for the reservation.
  561. Supported attributes:
  562. .RS
  563. .IP "qmove=<job ID>" 5
  564. Converts a normal job designated by
  565. .I job ID
  566. into a reservation job that will run
  567. as soon as possible. Creates the
  568. reservation with its queue and moves the job into the reservation's
  569. queue.
  570. Uses the resources requested by the job to create the reservation.
  571. When the reservation is created, it inherits its resources from the job,
  572. not from the resources requested through the
  573. .B pbs_rsub
  574. command.
  575. You can use the
  576. .I -I
  577. option to specify a timeout for the conversion. If you use the
  578. .B qmove
  579. option to convert a job to a reservation, and the reservation is not
  580. confirmed within the timeout period, the reservation is deleted. The
  581. default timeout period is
  582. .I 10 seconds.
  583. There is no option for this kind of reservation to be unconfirmed.
  584. To specify the timeout, you must give a negative value for the
  585. .I -I
  586. option. For example, to specify a timeout of 300 seconds:
  587. pbs_rsub -Wqmove=<job ID> -I -300
  588. The
  589. .I -R
  590. and
  591. .I -E
  592. options to
  593. .B pbs_rsub
  594. are disabled when using the
  595. .I qmove=<job ID>
  596. attribute.
  597. Some shells require that you enclose a job array ID in double quotes.
  598. .RE
  599. .IP "--version" 8
  600. The
  601. .B pbs_rsub
  602. command returns its PBS version information and exits.
  603. This option can only be used alone.
  604. .SH OUTPUT
  605. The
  606. .B pbs_rsub
  607. command returns the reservation identifier.
  608. .br
  609. For an advance reservation, this has the form
  610. .IP
  611. .I R<NNNN>.<server name>
  612. .LP
  613. where
  614. .I NNNN
  615. is a unique integer. The associated queue's name is the prefix,
  616. .I R<NNNN>.
  617. For a standing reservation, this has the form
  618. .IP
  619. .I S<NNNN>.<server name>
  620. .LP
  621. where
  622. .I NNNN
  623. is a unique integer. The associated queue's name is the prefix,
  624. .I S<NNNN>.
  625. .SH FORMATS
  626. .IP "Datetime format"
  627. .I "[[[[CC]YY]MM]DD]hhmm[.SS]"
  628. .IP "Reservation name"
  629. String up to 236 characters in length. It must consist of printable,
  630. non-white space characters with the first character alphabetic. The
  631. first character must be alphabetic, numeric, plus sign, dash or minus,
  632. or underscor. The name must not contain special characters.
  633. .SH SEE ALSO
  634. The
  635. .B PBS Professional User's Guide,
  636. the
  637. .B PBS Professional Administrator's Guide,
  638. .br
  639. pbs_resv_attributes(7B),
  640. pbs_rdel(1B),
  641. pbs_rstat(1B),
  642. qmove(1B),
  643. qsub(1B)