logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

qrls.1p (8122B)


  1. '\" et
  2. .TH QRLS "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. qrls
  12. \(em release batch jobs
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. qrls \fB[\fR-h \fIhold_list\fB] \fIjob_identifier\fR...
  17. .fi
  18. .SH DESCRIPTION
  19. A batch job might have one or more holds, which prevent the batch job
  20. from executing. A batch job from which all the holds have been removed
  21. becomes eligible for execution and is said to have been released. A
  22. batch job hold is removed by sending a request to the batch server that
  23. manages the batch job. The
  24. .IR qrls
  25. utility is a user-accessible client of batch services that requests
  26. holds be removed from one or more batch jobs.
  27. .P
  28. The
  29. .IR qrls
  30. utility shall remove one or more holds from those batch jobs for which
  31. a batch
  32. .IR job_identifier
  33. is presented to the utility.
  34. .P
  35. The
  36. .IR qrls
  37. utility shall remove holds from batch jobs in the order in which their
  38. batch
  39. .IR job_identifier s
  40. are presented to the utility.
  41. .P
  42. If the
  43. .IR qrls
  44. utility fails to process a batch
  45. .IR job_identifier
  46. successfully, the utility shall proceed to process the remaining batch
  47. .IR job_identifier s,
  48. if any.
  49. .P
  50. The
  51. .IR qrls
  52. utility shall remove holds on each batch job by sending a
  53. .IR "Release Job Request"
  54. to the batch server that manages the batch job.
  55. .P
  56. The
  57. .IR qrls
  58. utility shall not exit until the holds have been removed from the batch
  59. job corresponding to each successfully processed batch
  60. .IR job_identifier .
  61. .SH OPTIONS
  62. The
  63. .IR qrls
  64. utility shall conform to the Base Definitions volume of POSIX.1\(hy2017,
  65. .IR "Section 12.2" ", " "Utility Syntax Guidelines".
  66. .P
  67. The following option shall be supported by the implementation:
  68. .IP "\fB\-h\ \fIhold_list\fR" 10
  69. Define the types of holds to be removed from the batch job.
  70. .RS 10
  71. .P
  72. The
  73. .IR qrls
  74. .BR \-h
  75. option shall accept a value for the
  76. .IR hold_list
  77. option-argument that is a string of alphanumeric characters in the
  78. portable character set (see the Base Definitions volume of POSIX.1\(hy2017,
  79. .IR "Section 6.1" ", " "Portable Character Set").
  80. .P
  81. The
  82. .IR qrls
  83. utility shall accept a value for the
  84. .IR hold_list
  85. option-argument that is a string of one or more of the characters
  86. .BR 'u' ,
  87. .BR 's' ,
  88. or
  89. .BR 'o' ,
  90. or the single character
  91. .BR 'n' .
  92. .P
  93. For each unique character in the
  94. .IR hold_list
  95. option-argument, the
  96. .IR qrls
  97. utility shall add a value to the
  98. .IR Hold_Types
  99. attribute of the batch job as follows, each representing a different
  100. hold type:
  101. .IP "\fRu\fP" 6
  102. USER
  103. .IP "\fRs\fP" 6
  104. SYSTEM
  105. .IP "\fRo\fP" 6
  106. OPERATOR
  107. .P
  108. If any of these characters are duplicated in the
  109. .IR hold_list
  110. option-argument, the duplicates shall be ignored.
  111. .P
  112. An existing
  113. .IR Hold_Types
  114. attribute can be cleared by the following hold type:
  115. .IP "\fRn\fP" 6
  116. NO_HOLD
  117. .P
  118. The
  119. .IR qrls
  120. utility shall consider it an error if any hold type other than
  121. .BR 'n'
  122. is combined with hold type
  123. .BR 'n' .
  124. .P
  125. Strictly conforming applications shall not repeat any of the characters
  126. .BR 'u' ,
  127. .BR 's' ,
  128. .BR 'o' ,
  129. or
  130. .BR 'n'
  131. within the
  132. .IR hold_list
  133. option-argument. The
  134. .IR qrls
  135. utility shall permit the repetition of characters, but shall not assign
  136. additional meaning to the repeated characters.
  137. .P
  138. An implementation may define other hold types. The conformance document
  139. for an implementation shall describe any additional hold types, how
  140. they are specified, their internal behavior, and how they affect the
  141. behavior of the utility.
  142. .P
  143. If the
  144. .BR \-h
  145. option is not presented to the
  146. .IR qrls
  147. utility, the implementation shall remove the USER hold in the
  148. .IR Hold_Types
  149. attribute.
  150. .RE
  151. .SH OPERANDS
  152. The
  153. .IR qrls
  154. utility shall accept one or more operands that conform to the syntax
  155. for a batch
  156. .IR job_identifier
  157. (see
  158. .IR "Section 3.3.1" ", " "Batch Job Identifier").
  159. .SH STDIN
  160. Not used.
  161. .SH "INPUT FILES"
  162. None.
  163. .SH "ENVIRONMENT VARIABLES"
  164. The following environment variables shall affect the execution of
  165. .IR qrls :
  166. .IP "\fILANG\fP" 10
  167. Provide a default value for the internationalization variables that are
  168. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  169. .IR "Section 8.2" ", " "Internationalization Variables"
  170. the precedence of internationalization variables used to determine the
  171. values of locale categories.)
  172. .IP "\fILC_ALL\fP" 10
  173. If set to a non-empty string value, override the values of all the
  174. other internationalization variables.
  175. .IP "\fILC_CTYPE\fP" 10
  176. Determine the locale for the interpretation of sequences of bytes of
  177. text data as characters (for example, single-byte as opposed to
  178. multi-byte characters in arguments).
  179. .IP "\fILC_MESSAGES\fP" 10
  180. .br
  181. Determine the locale that should be used to affect the format and
  182. contents of diagnostic messages written to standard error.
  183. .IP "\fILOGNAME\fP" 10
  184. Determine the login name of the user.
  185. .SH "ASYNCHRONOUS EVENTS"
  186. Default.
  187. .SH STDOUT
  188. None.
  189. .SH STDERR
  190. The standard error shall be used only for diagnostic messages.
  191. .SH "OUTPUT FILES"
  192. None.
  193. .SH "EXTENDED DESCRIPTION"
  194. None.
  195. .SH "EXIT STATUS"
  196. The following exit values shall be returned:
  197. .IP "\00" 6
  198. Successful completion.
  199. .IP >0 6
  200. An error occurred.
  201. .SH "CONSEQUENCES OF ERRORS"
  202. In addition to the default behavior, the
  203. .IR qrls
  204. utility shall not be required to write a diagnostic message to standard
  205. error when the error reply received from a batch server indicates that
  206. the batch
  207. .IR job_identifier
  208. does not exist on the server. Whether or not the
  209. .IR qrls
  210. utility waits to output the diagnostic message while attempting to
  211. locate the job on other servers is implementation-defined.
  212. .LP
  213. .IR "The following sections are informative."
  214. .SH "APPLICATION USAGE"
  215. None.
  216. .SH EXAMPLES
  217. None.
  218. .SH RATIONALE
  219. The
  220. .IR qrls
  221. utility allows users, operators, and administrators to remove holds
  222. from jobs.
  223. .P
  224. The
  225. .IR qrls
  226. utility does not support any job selection options or wildcard
  227. arguments. Users may acquire a list of jobs selected by attributes
  228. using the
  229. .IR qselect
  230. utility. For example, a user could select all of their held jobs.
  231. .P
  232. The
  233. .BR \-h
  234. option allows the user to specify the type of hold that is to be
  235. removed. This option allows for USER, SYSTEM, OPERATOR, and
  236. implementation-defined hold types. The batch server that manages the
  237. batch job will verify whether the user is authorized to remove the
  238. specified hold for the batch job. If more than one type of hold has
  239. been placed on the batch job, a user may wish to remove only some of
  240. them.
  241. .P
  242. Mail is not required on release because the administrator has the tools
  243. and libraries to build this option if required.
  244. .P
  245. The
  246. .IR qrls
  247. utility is a new utility \fIvis-a-vis\fP existing practice; it has been
  248. defined in this volume of POSIX.1\(hy2017 as the natural complement to the
  249. .IR qhold
  250. utility.
  251. .SH "FUTURE DIRECTIONS"
  252. The
  253. .IR qrls
  254. utility may be removed in a future version.
  255. .SH "SEE ALSO"
  256. .IR "Chapter 3" ", " "Batch Environment Services",
  257. .IR "\fIqhold\fR\^",
  258. .IR "\fIqselect\fR\^"
  259. .P
  260. The Base Definitions volume of POSIX.1\(hy2017,
  261. .IR "Section 6.1" ", " "Portable Character Set",
  262. .IR "Chapter 8" ", " "Environment Variables",
  263. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  264. .\"
  265. .SH COPYRIGHT
  266. Portions of this text are reprinted and reproduced in electronic form
  267. from IEEE Std 1003.1-2017, Standard for Information Technology
  268. -- Portable Operating System Interface (POSIX), The Open Group Base
  269. Specifications Issue 7, 2018 Edition,
  270. Copyright (C) 2018 by the Institute of
  271. Electrical and Electronics Engineers, Inc and The Open Group.
  272. In the event of any discrepancy between this version and the original IEEE and
  273. The Open Group Standard, the original IEEE and The Open Group Standard
  274. is the referee document. The original Standard can be obtained online at
  275. http://www.opengroup.org/unix/online.html .
  276. .PP
  277. Any typographical or formatting errors that appear
  278. in this page are most likely
  279. to have been introduced during the conversion of the source files to
  280. man page format. To report such errors, see
  281. https://www.kernel.org/doc/man-pages/reporting_bugs.html .