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

qmsg.1p (8114B)


  1. '\" et
  2. .TH QMSG "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. qmsg
  12. \(em send message to batch jobs
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. qmsg \fB[\fR-EO\fB] \fImessage_string job_identifier\fR...
  17. .fi
  18. .SH DESCRIPTION
  19. To send a message to a batch job is to request that a server write a
  20. message string into one or more output files of the batch job. A
  21. message is sent to a batch job by a request to the batch server that
  22. manages the batch job. The
  23. .IR qmsg
  24. utility is a user-accessible batch client that requests the sending of
  25. messages to one or more batch jobs.
  26. .P
  27. The
  28. .IR qmsg
  29. utility shall write messages into the files of batch jobs by sending a
  30. .IR "Job Message Request"
  31. to the batch server that manages the batch job. The
  32. .IR qmsg
  33. utility shall not directly write the message into the files of the
  34. batch job.
  35. .P
  36. The
  37. .IR qmsg
  38. utility shall send a
  39. .IR "Job Message Request"
  40. for those batch jobs, and only those batch jobs, for which a batch
  41. .IR job_identifier
  42. is presented to the utility.
  43. .P
  44. The
  45. .IR qmsg
  46. utility shall send
  47. .IR "Job Message Request" s
  48. for batch jobs in the order in which their batch
  49. .IR job_identifier s
  50. are presented to the utility.
  51. .P
  52. If the
  53. .IR qmsg
  54. utility fails to process any batch
  55. .IR job_identifier
  56. successfully, the utility shall proceed to process the remaining batch
  57. .IR job_identifier s,
  58. if any.
  59. .P
  60. The
  61. .IR qmsg
  62. utility shall not exit before a
  63. .IR "Job Message Request"
  64. has been sent to the server that manages the batch job that corresponds
  65. to each successfully processed batch
  66. .IR job_identifier .
  67. .SH OPTIONS
  68. The
  69. .IR qmsg
  70. utility shall conform to the Base Definitions volume of POSIX.1\(hy2017,
  71. .IR "Section 12.2" ", " "Utility Syntax Guidelines".
  72. .P
  73. The following options shall be supported by the implementation:
  74. .IP "\fB\-E\fP" 10
  75. Specify that the message is written to the standard error of each batch
  76. job.
  77. .RS 10
  78. .P
  79. The
  80. .IR qmsg
  81. utility shall write the message into the standard error of the batch
  82. job.
  83. .RE
  84. .IP "\fB\-O\fP" 10
  85. Specify that the message is written to the standard output of each
  86. batch job.
  87. .RS 10
  88. .P
  89. The
  90. .IR qmsg
  91. utility shall write the message into the standard output of the batch
  92. job.
  93. .RE
  94. .P
  95. If neither the
  96. .BR \-O
  97. nor the
  98. .BR \-E
  99. option is presented to the
  100. .IR qmsg
  101. utility, the utility shall write the message into an
  102. implementation-defined file. The conformance document for the
  103. implementation shall describe the name and location of the
  104. implementation-defined file. If both the
  105. .BR \-O
  106. and the
  107. .BR \-E
  108. options are presented to the
  109. .IR qmsg
  110. utility, then the utility shall write the messages to both standard
  111. output and standard error.
  112. .SH OPERANDS
  113. The
  114. .IR qmsg
  115. utility shall accept a minimum of two operands,
  116. .IR message_string
  117. and one or more batch
  118. .IR job_identifier s.
  119. .P
  120. The
  121. .IR message_string
  122. operand shall be the string to be written to one or more output files
  123. of the batch job followed by a
  124. <newline>.
  125. If the string contains
  126. <blank>
  127. characters, then the application shall ensure that the string is
  128. quoted. The
  129. .IR message_string
  130. shall be encoded in the portable character set (see the Base Definitions volume of POSIX.1\(hy2017,
  131. .IR "Section 6.1" ", " "Portable Character Set").
  132. .P
  133. All remaining operands are batch
  134. .IR job_identifier s
  135. that conform to the syntax for a batch
  136. .IR job_identifier
  137. (see
  138. .IR "Section 3.3.1" ", " "Batch Job Identifier").
  139. .SH STDIN
  140. Not used.
  141. .SH "INPUT FILES"
  142. None.
  143. .SH "ENVIRONMENT VARIABLES"
  144. The following environment variables shall affect the execution of
  145. .IR qmsg :
  146. .IP "\fILANG\fP" 10
  147. Provide a default value for the internationalization variables that are
  148. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  149. .IR "Section 8.2" ", " "Internationalization Variables"
  150. the precedence of internationalization variables used to determine the
  151. values of locale categories.)
  152. .IP "\fILC_ALL\fP" 10
  153. If set to a non-empty string value, override the values of all the
  154. other internationalization variables.
  155. .IP "\fILC_CTYPE\fP" 10
  156. Determine the locale for the interpretation of sequences of bytes of
  157. text data as characters (for example, single-byte as opposed to
  158. multi-byte characters in arguments).
  159. .IP "\fILC_MESSAGES\fP" 10
  160. .br
  161. Determine the locale that should be used to affect the format and
  162. contents of diagnostic messages written to standard error.
  163. .IP "\fILOGNAME\fP" 10
  164. Determine the login name of the user.
  165. .SH "ASYNCHRONOUS EVENTS"
  166. Default.
  167. .SH STDOUT
  168. None.
  169. .SH STDERR
  170. The standard error shall be used only for diagnostic messages.
  171. .SH "OUTPUT FILES"
  172. None.
  173. .SH "EXTENDED DESCRIPTION"
  174. None.
  175. .SH "EXIT STATUS"
  176. The following exit values shall be returned:
  177. .IP "\00" 6
  178. Successful completion.
  179. .IP >0 6
  180. An error occurred.
  181. .SH "CONSEQUENCES OF ERRORS"
  182. In addition to the default behavior, the
  183. .IR qmsg
  184. utility shall not be required to write a diagnostic message to standard
  185. error when the error reply received from a batch server indicates that
  186. the batch
  187. .IR job_identifier
  188. does not exist on the server. Whether or not the
  189. .IR qmsg
  190. utility waits to output the diagnostic message while attempting to
  191. locate the job on other servers is implementation-defined.
  192. .LP
  193. .IR "The following sections are informative."
  194. .SH "APPLICATION USAGE"
  195. None.
  196. .SH EXAMPLES
  197. None.
  198. .SH RATIONALE
  199. The
  200. .IR qmsg
  201. utility allows users to write messages into the output files of running
  202. jobs. Users, including operators and administrators, have a number of
  203. occasions when they want to place messages in the output files of a
  204. batch job. For example, if a disk that is being used by a batch job is
  205. showing errors, the operator might note this in the standard error
  206. stream of the batch job.
  207. .P
  208. The options of the
  209. .IR qmsg
  210. utility provide users with the means of placing the message in the
  211. output stream of their choice. The default output stream for the
  212. message\(emif the user does not designate an output stream\(emis
  213. implementation-defined, since many implementations will provide, as
  214. an extension to this volume of POSIX.1\(hy2017, a log file that shows the history of utility
  215. execution.
  216. .P
  217. If users wish to send a message to a set of jobs that meet a selection
  218. criteria, the
  219. .IR qselect
  220. utility can be used to acquire the appropriate list of job
  221. identifiers.
  222. .P
  223. The
  224. .BR \-E
  225. option allows users to place the message in the standard error stream
  226. of the batch job.
  227. .P
  228. The
  229. .BR \-O
  230. option allows users to place the message in the standard output stream
  231. of the batch job.
  232. .P
  233. Historically, the
  234. .IR qmsg
  235. utility is an existing practice in the offerings of one or more
  236. implementors of an NQS-derived batch system. The utility has been found
  237. to be useful enough that it deserves to be included in this volume of POSIX.1\(hy2017.
  238. .SH "FUTURE DIRECTIONS"
  239. The
  240. .IR qmsg
  241. utility may be removed in a future version.
  242. .SH "SEE ALSO"
  243. .IR "Chapter 3" ", " "Batch Environment Services",
  244. .IR "\fIqselect\fR\^"
  245. .P
  246. The Base Definitions volume of POSIX.1\(hy2017,
  247. .IR "Section 6.1" ", " "Portable Character Set",
  248. .IR "Chapter 8" ", " "Environment Variables",
  249. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  250. .\"
  251. .SH COPYRIGHT
  252. Portions of this text are reprinted and reproduced in electronic form
  253. from IEEE Std 1003.1-2017, Standard for Information Technology
  254. -- Portable Operating System Interface (POSIX), The Open Group Base
  255. Specifications Issue 7, 2018 Edition,
  256. Copyright (C) 2018 by the Institute of
  257. Electrical and Electronics Engineers, Inc and The Open Group.
  258. In the event of any discrepancy between this version and the original IEEE and
  259. The Open Group Standard, the original IEEE and The Open Group Standard
  260. is the referee document. The original Standard can be obtained online at
  261. http://www.opengroup.org/unix/online.html .
  262. .PP
  263. Any typographical or formatting errors that appear
  264. in this page are most likely
  265. to have been introduced during the conversion of the source files to
  266. man page format. To report such errors, see
  267. https://www.kernel.org/doc/man-pages/reporting_bugs.html .