Category:Sirius Mods messages: Difference between revisions
(Created page with "The <var class="product">Sirius Mods</var> messages use <var class="product">Model 204</var> message processing; each of them has a prefix of <code>MSIR</code> and has sev...") |
mNo edit summary |
||
| Line 38: | Line 38: | ||
You can [{{fullurl:{{FULLPAGENAMEE}}|action=pdfbook}} use this link] to create a PDF file that contains all the pages in this category. | You can [{{fullurl:{{FULLPAGENAMEE}}|action=pdfbook}} use this link] to create a PDF file that contains all the pages in this category. | ||
[[Category: | [[Category:Sirius messages| Sirius Mods messages]] | ||
Revision as of 21:49, 5 November 2014
The Sirius Mods messages use Model 204 message processing; each of them has a
prefix of MSIR and has several attributes, some of which you can control. For example,
the following command causes message MSIR.0329 to stop being displayed at the
user's terminal:
MSGCTL MSIR.0329 NOTERM
For information about controlling the message-processing attributes, see the MSGCTL command description.
Unless otherwise specified, all MSIR messages indicate that an error occurred and the requested operation may not have completed successfully; the default attributes for the messages are:
- CLASS=E
- COUNT
- TERM
- Batch return code=4
- Online return code=0
- They are audited as ER messages on the audit trail.
A number of the MSIR messages are described as being informational or warning messages. The purpose of these messages may be to warn you, or simply to provide some information; they do not in themselves indicate failure of an operation. Unless otherwise indicated, the above list of attributes is changed for informational or warning messages as follows:
- CLASS=I
- NOCOUNT
- Batch return code=0
- Online return code=0
- They are audited as MS messages on the audit trail.
You can use this link to create a PDF file that contains all the pages in this category.
This category currently contains no pages or media.