MSGCTL command: Difference between revisions
RPuszewski (talk | contribs) |
RPuszewski (talk | contribs) No edit summary |
||
Line 40: | Line 40: | ||
<tr> | <tr> | ||
<th>msg-option</th> | <th>msg-option</th> | ||
<td>If none of the options are specified, the current options are displayed. | <td>If none of the options are specified, the current options are displayed (V7.9 or later). | ||
Otherwise, one of the following: | Otherwise, one of the following: | ||
<table> | <table> | ||
Line 97: | Line 97: | ||
<tr> <th><var>NOCOUNT</var></th> | <tr> <th><var>NOCOUNT</var></th> | ||
<td>Does not increment, by one, the message count whenever this message is displayed. </td> </tr> | <td>Does not increment, by one, the message count whenever this message is displayed. </td> </tr> | ||
<tr> <th><var>NOCTL</var></th> | |||
<td>This option may only be set during Model 204 initialization (ie. prior to CCAIN USER 0 processing). | |||
If a message is set with this option, it can not be changed by MSGCTL during the entire run.</td> </tr> | |||
<tr> <th><var>NODUMP </var></th> | <tr> <th><var>NODUMP </var></th> |
Revision as of 19:20, 26 February 2024
Setting message output
Summary
- Privileges
- System administrator
- Function
- Displays or specifies the actions to be taken when Model 204 produces a particular error or informational message.
Syntax
MSGCTL {M204 | USER | MSIR}.msg-number [msg-option [msg-option]... ] [CLASS={P | I | E}] [RETCODEO=online-retcode] [RETCODEB=batch-retcode]
Where:
M204 | A standard Model 204 message. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
USER | A user message. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MSIR | A Sirius message. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
msg-number | The four-digit number of the message. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
msg-option | If none of the options are specified, the current options are displayed (V7.9 or later).
Otherwise, one of the following:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CLASS |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
RETCODEO | A job step return code in the range 1 to 255 to be associated with the message in Online runs. The actual job step return code is the maximum return code of all messages issued. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
RETCODEB | A job step return code in the range 1 to 255 to be associated with the message in batch runs. The actual job step return code is the maximum return code of all messages issued. |
See Job step return codes for a description and list of job step return codes.
Syntax notes
- A period, with no space before or after, must be specified between the message prefix, M204 or USER, and the message number.
- Any number of nonconflicting options can be specified in the MSGCTL command. If conflicting options are specified, for example, PREFIX and NOPREFIX, the option specified last takes effect.
- You can specify the MSGCTL command before the User 0 parameter line in the CCAIN stream. This lets you format messages displayed during initialization and recovery.
- The MSGCTL message options — AUDIT, AUDITAD, AUDITMS, AUDITRK — are mutually exclusive. If you enter multiple options for a message, the last option listed is processed.
- The COUNT option is a separate process and can be used with the AUDIT, AUDITAD, AUDITMS, or AUDITRK option, as needed.
Hierarchical evaluation of message types
The hierarchical structure of messages types is as follows:
- The NOAUDITER option lowers an ER message to an RK message type.
- The NOAUDITRK option lowers an RK message to an AD message type.
- The NOAUDITAD option lowers an AD message to an MS message type.
- The NOAUDITMS option lowers an MS message, so that it is not audited, as though you had used the NOAUDIT option.
The NOAUDITxx option only processes a message of the xx type. However, NOAUDIT works on any message type.
If NOAUDITxx is specified for a message that is not of type xx, the following message is returned:
M204.1047 NOAUDITxx IS AN INVALID PARAMETER FOR THIS MESSAGE
Example
The following example displays the current options for the standard Model 204 password prompt:
MSGCTL M204.0347 Which returns: MSGCTL M204.0347 NOCAN NOOPR NOCOUNT PREFIX TERM NOSAVE NOSNAP NODUMP RETCODEB=0 RETCODEO=0 CLASS=P AUDIT AUDITMS NOUPPER
The following example suppresses the display of the message prefix and number associated with the standard Model 204 password prompt:
MSGCTL M204.0347 NOPREFIX
Usage notes
- The MSGCTL command lets the system manager change the way Model 204 processes a particular error or informational message. Changes made to a message affect all users in the Online.
- You can use the MSGCTL command to change processing for either standard Model 204 messages with a Model 204 prefix or for messages with a user prefix developed by the installation. Note that you can also use the MSGCTL parameter to control the display of message prefixes as well as error and informational messages on the user's terminal. User messages are built in the MSGU module distributed with Model 204 and described in the Model 204 installation documentation.
- Model 204 handles different message event conditions in different ways. For example:
- A message can be displayed on the operator's console.
- A message can be displayed on the user's terminal.
- A message can be written to the journal or audit trail data set.
- An error can result in the production of a SNAP.
- For all Model 204 message event conditions, the Model 204 message documentation lists the error number, the text of the message, and the default action that is taken when the event occurs.
Understanding the NOCOUNT option
Attention: Rocket Software strongly recommends that you do not change or suppress the COUNT option that is assigned to some messages. The SOUL compiler depends on using the COUNT option to track errors in your program. If no errors can be reported, your program will seem to compile, only to abend during the run. Also, the lack of messages in your Model 204 journal, audit trail, or other job output can result in the inability to trace and diagnose problems.
How the MSGCTL command can override both the MSGCTL and DEBUGUL parameters
If you use the MSGCTL command, and suppress the display of a message by using the NOTERM keyword, then no matter how the MSGCTL or DEBUGUL parameters are set, the message does not go to the terminal. Conversely, if you want messages displayed at the terminal, enter the MSGCTL command using the following syntax:
MSGCTL {M204 | USER}.msg-number TERM
Understanding the NOACTION option
Error messages have a one-byte indicator that informs message processing whether the message needs to be processed and whether the message has been changed using MSGTL. If a message does not need processing, Model 204 resumes the main processing.
Note: NOACTION has no effect on a restart or a termination message.