MSGCTL command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
 
(18 intermediate revisions by 9 users not shown)
Line 1: Line 1:
<span class="pageSubtitle">Setting message output</span>
==Summary==
==Summary==
<dl>
<dl>
Line 4: Line 6:
<dd>System administrator
<dd>System administrator
<dt>Function
<dt>Function
<dd>Specifies the actions to be taken when <var class="product">Model&nbsp;204</var> produces a particular error or informational message
<dd>Displays or specifies the actions to be taken when <var class="product">Model&nbsp;204</var> produces a particular error or informational message.
</dl>
</dl>
==Syntax==
==Syntax==
<p class="syntax">MSGCTL {M204 | USER}.msg-number  
<p class="syntax">MSGCTL {M204 | USER | MSIR}.<span class="term">msg-number</span>
  [msg-option [msg-option]... ]
  [<span class="term">msg-option</span> [<span class="term">msg-option</span>]... ]
  [CLASS={P | I | E}] [RETCODEO=online-retcode]  
  [CLASS={P | I | E}] [RETCODEO=<span class="term">online-retcode</span>]  
  [RETCODEB=batch-retcode]
  [RETCODEB=<span class="term">batch-retcode</span>]
</p>
</p>
   
   
Line 17: Line 20:
<tr>
<tr>
<th><var>M204</var></th>
<th><var>M204</var></th>
<td> specifies a standard <var class="product">Model&nbsp;204</var> message.</td>
<td>A standard <var class="product">Model&nbsp;204</var> message.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>USER</var></th>
<th><var>USER</var></th>
<td> specifies a user message.</td>
<td>A user message.</td>
</tr>
</tr>
   
   
<tr>
<th><var>MSIR</var></th>
<td>A Sirius message.</td>
</tr>
<tr>
<tr>
<th>msg-number</th>
<th>msg-number</th>
<td> is the four-digit number of the message.</td>
<td>The four-digit number of the message.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>msg-option</th>
<th>msg-option</th>
<td> is one of the following:  
<td>If none of the options are specified, the current options are displayed (V7.9 or later).
<table>
Otherwise, one of the following:  
<caption>MSGCTL command message options </caption>
<table>  
   
<tr class="head">  
<tr> <th>
<th><p>Option</p></th>  
<p>Option</p>
<th><p>Action</p></th>  
</th> <th>
</tr>
<p>Action...</p>
</th> </tr>
    
    
<tr> <th><var>AUDITAD  </var></th> <td>
<tr> <th><var>AUDITAD  </var></th>  
<p>Puts the specified message on the audit trail as an AD line.</p>
<td>Puts the specified message on the audit trail as an AD line.</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>AUDITER</var></th>  
<p>AUDITER</p>
<td>Puts the specified message on the audit trail as an ER line.</td> </tr>
</var></th> <td>
<p>Puts the specified message on the audit trail as an ER line.</p>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>AUDITMS</var></th>  
<p>AUDITMS</p>
<td>Puts the specified error message on the audit trail as an MS line.</td> </tr>
</var></th> <td>
<p>Puts the specified error message on the audit trail as an MS line.</p>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>AUDITRK</var></th>  
<p>AUDITRK</p>
<td>Puts the specified message on the audit as an RK line. </td> </tr>
</var></th> <td>Puts the specified message on the audit as an RK line. </td> </tr>
 
<tr> <th><var>CAN</var></th>
<td>Causes the message to become a request cancellation message. </td> </tr>
 
   
   
<tr> <th><var>
<tr> <th><var>COUNT</var></th>  
<p>COUNT</p>
<td>Increments, by one, the message count whenever this message is issued. If the message count exceeds the value of the <var>[[ERMX parameter|ERMX]]</var> parameter, the user's session and processing are stopped. </td> </tr>
</var></th> <td>Increments, by one, the message count whenever this message is issued. If the message count exceeds the value of the ERMX parameter, the user's session and processing are stopped. </td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>DUMPALL</var></th>  
<p>DUMPALL</p>
<td>Dumps the entire <var class="product">Model&nbsp;204</var> region. Provides the maximum amount of information for problem determination. </td> </tr>
</var></th> <td>Dumps the entire <var class="product">Model&nbsp;204</var> region. Provides the maximum amount of information for problem determination. </td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>
<p>NOACTION </p>
NOACTION </var></th>  
</var></th> <td>
<td>Ignores the original option that was assigned the message and returns to main processing.
<p>Ignores the original option that was assigned the message and returns to main processing.</p>
</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOAUDIT</var></th>  
<p>NOAUDIT</p>
<td>Suppresses the auditing of a specific error message. Use with caution, since preventing certain messages from going to the journal could make problem diagnosis more difficult.
</var></th> <td>
<p>Suppresses the auditing of a specific error message.</p>
</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOAUDITAD</var></th>  
<p>NOAUDITAD</p>
<td>Puts the specified message on the audit trail as an MS line.  </td> </tr>
</var></th> <td>Puts the specified message on the audit trail as an MS line.   </td> </tr>
<tr> <th><var>NOAUDITER</var></th>  
<td>Puts the specified message on the audit trail as an RK line.</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOAUDITMS</var></th>  
<p>NOAUDITER</p>
<td>Suppresses auditing the specified MS message.</td> </tr>
</var></th> <td>
<p>Puts the specified message on the audit trail as an RK line.</p>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOAUDITRK</var></th>  
<p>NOAUDITMS</p>
<td>Put the specified message on the audit trail as an AD line.  </td> </tr>
</var></th> <td>
 
<p>Suppresses auditing the specified MS message.</p>
<tr> <th><var>NOAUDITW</var></th>  
<td>Suppresses the specified message on Janus Web threads if <var>[[WEBAUDIT parameter|WEBAUDIT]]</var>=1. Use with caution, since preventing certain messages from going to the journal could make problem diagnosis more difficult.
</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOCOUNT</var></th>  
<p>NOAUDITRK</p>
<td>Does not increment, by one, the message count whenever this message is displayed. </td> </tr>
</var></th> <td>Put the specified message on the audit trail as an AD line.   </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>
<tr> <th><var>NODUMP </var></th>  
<p>NOCOUNT</p>
<td>Does not generate a dump.</td> </tr>
</var></th> <td>Does not increment, by one, the message count whenever this message is displayed. </td> </tr>
   
   
<tr> <th><var>NODUMP </var></th> <td>
<tr> <th><var>NOOPR</var></th>  
<p>Does not generate a dump.</p>
<td>Does not display the specified message on the operator's console. </td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOPREFIX</var></th>  
<p>NOOPR</p>
<td>Suppresses the display of the message prefix and number. </td> </tr>
</var></th> <td>Does not display the specified message on the operator's console. </td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>NOPREFIX</p>
<th><var>NOSAVE</var></th>  
</var></th> <td>Suppresses the display of the message prefix and number.         </td> </tr>
<td>Does not save the specified message in the message save table. Note that messages sent to the operator and messages that cause SNAPs are always added to the message save table, regardless of the selection of the <var>SAVE</var> or <var>NOSAVE</var> options. </td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOSNAP</var></th>  
<p>NOSAVE</p>
<td>Suppresses the production of a SNAP when the specified error condition occurs. </td> </tr>
</var></th> <td>Does not save the specified message in the message save table. The user should note that messages sent to the operator and messages that cause SNAPs are always added to the message save table, regardless of the selection of the SAVE or NOSAVE options. </td> </tr>
   
   
<tr> <th><var>
<tr> <th><var> NOTERM</var></th>  
<p>NOSNAP</p>
<td>Does not display the specified message on the user's terminal or for single user jobs in CCAPRINT.
</var></th> <td>Suppresses the production of a SNAP when the specified error condition occurs. </td> </tr>
<p class="note"><b>Note: </b><var class="product">Model&nbsp;204</var> passes return codes back in login and logout messages; if you set the <var>NOTERM</var> option for login and logout messages, you cannot get the return code.</p>
<tr> <th><var> NOTERM</var></th> <td>
<p>Does not display the specified message on the user's terminal or for single user jobs in CCAPRINT.</p>
<p><b>Note: </b><var class="product">Model&nbsp;204</var> passes return codes back in login and logout messages; if you set the NOTERM option for login and logout messages you cannot get the return code.</p>
</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>NOUP</var> or <var>NOUPPER</var></th>
<p>OPR</p>
<td> Reverses the effect of a previous UP option, thus returning the specified message to its original displayed format. </td> </tr>
</var></th> <td>Displays the specified message message on the operator's console. </td> </tr>
 
<tr> <th><var>OPR</var></th>  
<td>Displays the specified message message on the operator's console. </td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>PREFIX</var></th>  
<p>PREFIX</p>
<td>Displays a message prefix (M204 or USER) and message number along with the message. </td> </tr>
</var></th> <td>Displays a message prefix (M204 or USER) and message number along with the message. </td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>SAVE</var></th>  
<p>SAVE</p>
<td>Puts a copy of the specified message on the message save table whenever that message is issued. Use the <var>[[VIEW command#VIEW ERRORS|VIEW ERRORS]]</var> command to examine the saved message.</td> </tr>
</var></th> <td>Puts a copy of the specified message on the message save table whenever that message is issued. Use the VIEW ERRORS command to examine the saved message.</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>SNAP</var></th>  
<p>SNAP</p>
<td><var>SNAP</var> produces the same information as <var>SNAPALL</var>. </td> </tr>
</var></th> <td>SNAP produces the same information as SNAPALL. </td> </tr>
   
   
<tr> <th><var>SNAPALL </var></th> <td>
<tr> <th><var>SNAPALL </var></th>  
<p>The SNAP includes all allocated storage except the <var class="product">Model&nbsp;204</var> load module.</p>
<td>The SNAP includes all allocated storage except the <var class="product">Model&nbsp;204</var> load module.</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>SNAPPDL</var></th>  
<p>SNAPPDL</p>
<td>The SNAP includes the registers, module map (alpha and address order), allocated storage map, pushdown list trace, user's server, KOMM, disk buffers containing <var class="product">Model&nbsp;204</var> file pages held by the current user (maximum of 4), file directory of current file, and patch information. </td> </tr>
</var></th> <td>The SNAP includes the registers, module map (alpha and address order), allocated storage map, pushdown list trace, user's server, KOMM, disk buffers containing <var class="product">Model&nbsp;204</var> file pages held by the current user (maximum of 4), file directory of current file, and patch information. </td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>SNAPSEL <i>n </i></p>
<th><var>SNAPSEL</var> n </th>  
</var></th> <td>
<td>SNAP includes everything in <var>SNAPPDL</var> as well as other items specified by <var class="term">n</var>. The settings for <var class="term">n</var> can be added together. For example, to output the disk buffers for Tables B and C on a divide-by-zero error:
<p>SNAP includes everything in SNAPPDL as well as other items specified by <i>n. </i>The settings for n can be added together. For example, to output the disk buffers for Tables B and C:</p>
<p class="code">MSGCTL M204.0554 SNAPSEL 6</p>
MSGCTL SNAPSEL 6 </td> </tr>
 
<table class="thJustBold">
<tr class="head">
<th>Value of <i>n</i></th>
<th>Result</th>
</tr>
 
<tr>
<th>1</th>
<td>Output all Table A and FCT disk buffers for the current file and no CCATEMP disk buffers.
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>  where <i>n</i>=1</p>
<th>2</th>  
</var></th> <td>
<td>Output all Table B disk buffers for the current file and no CCATEMP disk buffers.</td>  
<p>Output all Table A and FCT disk buffers for the current file and no CCATEMP disk buffers.</p>
</tr>
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>  where <i>n</i>=2</p>
<th>4</th>  
</var></th> <td>
<td>Output all Table C disk buffers for the current file and no CCATEMP disk buffers.</td>  
<p>Output all Table B disk buffers for the current file and no CCATEMP disk buffers.</p>
</tr>
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>  where <i>n</i>=4</p>
<th>8</th>  
</var></th> <td>
<td>Output all Table D disk buffers for the current file and no CCATEMP disk buffers.</td>  
<p>Output all Table C disk buffers for the current file and no CCATEMP disk buffers.</p>
</tr>
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>  where <i>n</i>=8</p>
<th>16</th>  
</var></th> <td>
<td>Output the disk buffers requested by the previous settings for all files open by this user and no CCATEMP disk buffers. This setting directs the buffer output and coordinates with one of the previous settings.</td>  
<p>Output all Table D disk buffers for the current file and no CCATEMP disk buffers.</p>
</tr>
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>  where <i>n</i>=16</p>
<th>32</th>  
</var></th> <td>
<td>Output all data structures except those which pertain to record locking, resource locking and disk buffers.</td>  
<p>Output the disk buffers requested by the previous settings for all files open by this user and no CCATEMP disk buffers. This setting directs the buffer output and coordinates with one of the previous settings.</p>
</tr>
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>  where <i>n</i>=32</p>
<th>64</th>  
</var></th> <td>
<td>Output those data structures which pertain to record locking and resource locking.</td>  
<p>Output all data structures except those which pertain to record locking, resource locking and disk buffers.</p>
</tr>
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p> where <i>n</i>=64</p>
<th>128</th>  
</var></th> <td>
<td>Output all CCATEMP disk buffers and no <var class="product">Model&nbsp;204</var> file disk buffers.</td>  
<p>Output those data structures which pertain to record locking and resource locking.</p>
</tr>
</td> </tr>
</table>
   
   
<tr> <th><var>
<tr>  
<p>  where <i>n</i>=128</p>
<th><var>TERM</var></th>  
</var></th> <td>
<td>Causes the specified message to be displayed on the user's terminal or for single user jobs in CCAPRINT.   </td> </tr>
<p>Output all CCATEMP disk buffers and no <var class="product">Model&nbsp;204</var> file disk buffers.</p>
</td> </tr>
   
   
<tr> <th><var>
<tr>  
<p>TERM</p>
<th><var>UP</var> or <var>UPPER</var></th>
</var></th> <td>Causes the specified message to be displayed on the user's terminal or for single user jobs in CCAPRINT.   </td> </tr>
<td> Forces the specified message to be displayed in uppercase. </td> </tr>
 
</table>
</table>
</td>
</td>
Line 219: Line 209:
<tr>
<tr>
<th><var>CLASS</var></th>
<th><var>CLASS</var></th>
<td> parameters are used on only messages that have been suppressed in an application subsystem (APSY). The CLASS parameters have no effect on messages appearing outside of an APSY. For example, if an APSY suppresses E (error) messages, you can reset the message to I (informational). It will then appear at the user terminal. If both I and E are suppressed, you can reset it to P (prompt) and the message will appear at the terminal.
<td><table>  
<table>  
<tr>
<tr>
<th><var>CLASS=P</var></th>
<th><var>CLASS=P</var></th>
<td> resets the message so that it is treated as a prompting message. Since you cannot suppress the printing of prompting messages at the terminal, the message is displayed at the APSY user's terminal.  
<td>Resets the message so that it is treated as a prompting message. Since you cannot suppress the printing of prompting messages at the terminal, the message is displayed at the APSY user's terminal.  
<p class="note"><b>Note:</b> <var>P</var> does not cause a prompt; it only forces the message to appear at the terminal in an APSY.</p>
<p class="note"><b>Note:</b> <var>P</var> does not cause a prompt; it only forces the message to appear at the terminal in an APSY.</p>
</td>
</td>
Line 230: Line 219:
<tr>
<tr>
<th><var>CLASS=I</var></th>
<th><var>CLASS=I</var></th>
<td> (informational) prevents the specified message from being printed at the terminal, within an APSY for which informational messages are suppressed.</td>
<td> (informational) Prevents the specified message from being printed at the terminal if the X'02' bit of the <var>[[MSGCTL parameter|MSGCTL]]</var> parameter is set.  Note that this bit is set within an APSY for which informational messages are suppressed.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>CLASS=E</var></th>
<th><var>CLASS=E</var></th>
<td> (error) prevents the specified message from being printed at the terminal within an APSY for which error messages are suppressed.</td>
<td> (error) Prevents the specified message from being printed at the terminal if the X'04' bit of the <var>[[MSGCTL parameter|MSGCTL]]</var> parameter is set.  Note that this bit is set within an APSY for which error messages are suppressed.</td>
</tr>
</tr>
   
   
Line 244: Line 233:
<tr>
<tr>
<th><var>RETCODEO</var></th>
<th><var>RETCODEO</var></th>
<td> specifies 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.</td>
<td>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.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>RETCODEB</var></th>
<th><var>RETCODEB</var></th>
<td> specifies 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.</td>
<td>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.</td>
</tr>
</tr>
</table>
</table>
<p>See the <var class="product">Model&nbsp;204</var> System Manager's Guide for a description of job step return codes. The <var class="product">Model&nbsp;204</var> Messages Manual lists the job step return codes.</p>
 
<p>
See [[Controlling system operations (CCAIN)#Job step return codes|Job step return codes]] for a description and list of job step return codes. </p>
 
===Syntax notes===
===Syntax notes===
<p>A period, with no space before or after, must be specified between the message prefix, M204 or USER, and the message number.</p>
<ul>
<p>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.</p>
<li>A period, with no space before or after, must be specified between the message prefix, <var>M204</var> or <var>USER</var>, and the message number.</li>
<p>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.</p>
 
<p>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. </p>
<li>Any number of nonconflicting options can be specified in the <var>MSGCTL</var> command. If conflicting options are specified, for example, <var>PREFIX</var> and <var>NOPREFIX</var>, the option specified last takes effect.</li>
<p>The COUNT option is a separate process and can be used with the AUDIT, AUDITAD, AUDITMS, or AUDITRK option, as needed.</p>
 
<li>You can specify the <var>MSGCTL</var> command before the User 0 parameter line in the CCAIN stream. This lets you format messages displayed during initialization and recovery.</li>
 
<li>The <var>MSGCTL</var> message options &mdash; <var>AUDIT</var>, <var>AUDITAD</var>, <var>AUDITMS</var>, <var>AUDITRK</var> &mdash; are mutually exclusive. If you enter multiple options for a message, the last option listed is processed. </li>
 
<li>The <var>COUNT</var> option is a separate process and can be used with the <var>AUDIT</var>, <var>AUDITAD</var>, <var>AUDITMS</var>, or <var>AUDITRK</var> option, as needed.</li>
</ul>
 
===Hierarchical evaluation of message types===
===Hierarchical evaluation of message types===
<p>The hierarchical structure of messages types is as follows:</p>
<p>The hierarchical structure of messages types is as follows:</p>
<ul>  
<ul>  
<li>
<li>The <var>NOAUDITER</var> option lowers an ER message to an RK message type.</li>
<p>The NOAUDITER option lowers an ER message to an RK message type.</p>
</li>
   
   
<li>
<li>The <var>NOAUDITRK</var> option lowers an RK message to an AD message type.</li>
<p>The NOAUDITRK option lowers an RK message to an AD message type.</p>
</li>
   
   
<li>
<li>The <var>NOAUDITAD</var> option lowers an AD message to an MS message type.</li>
<p>The NOAUDITAD option lowers an AD message to an MS message type.</p>
</li>
   
   
<li>
<li>The <var>NOAUDITMS</var> option lowers an MS message, so that it is not audited, as though you had used the <var>NOAUDIT</var> option.</li>
<p>The NOAUDITMS option lowers an MS message, so that it is not audited, as though you had used the NOAUDIT option.</p>
</ul>
</li>
 
</ul>
<p>
<p>The NOAUDITxx option only processes a message of the 'xx' type. However, NOAUDIT works on any message type.</p>
The <var>NOAUDIT<i>xx</i></var> option only processes a message of the <var class="term">xx</var> type. However, <var>NOAUDIT</var> works on any message type.</p>
<p>If NOAUDITxx is specified for a message that is not of type 'xx', the following message is returned:</p>
<p>
<p class="code">M204.1047 NOAUDITxx IS AN INVALID PARAMETER FOR THIS MESSAGE
If <var>NOAUDIT<i>xx</i></var> is specified for a message that is not of type <var class="term">xx</var>, the following message is returned:</p>
<p class="code">M204.1047 NOAUDIT<i>xx</i> IS AN INVALID PARAMETER FOR THIS MESSAGE
</p>
</p>


==Example==
==Example==
The following V7.9 example displays the current options for the standard <var class="product">Model&nbsp;204</var> password prompt:
<p class="code"><B>MSGCTL M204.0347</B>
Which returns:
<B>MSGCTL M204.0347  NOCAN NOOPR NOCOUNT PREFIX TERM NOSAVE NOSNAP NODUMP RETCODEB=0 RETCODEO=0 CLASS=P AUDIT AUDITMS NOUPPER</B>
</p>
The following example suppresses the display of the message prefix and number associated with the standard <var class="product">Model&nbsp;204</var> password prompt:
The following example suppresses the display of the message prefix and number associated with the standard <var class="product">Model&nbsp;204</var> password prompt:
<p class="code">MSGCTL M204.0347 NOPREFIX
<p class="code"><B>MSGCTL M204.0347 NOPREFIX</B>
</p>
</p>
==Usage notes==
==Usage notes==
<p>The MSGCTL command lets the system manager change the way <var class="product">Model&nbsp;204</var> processes a particular error or informational message. Changes made to a message affect all users in the Online.</p>
<ul>
<p>You can use the MSGCTL command to change processing for either standard <var class="product">Model&nbsp;204</var> messages with a <var class="product">Model&nbsp;204</var> 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 <var class="product">Model&nbsp;204</var> and described in the <var class="product">Model&nbsp;204</var> Installation Guide.</p>
<li>The <var>MSGCTL</var> command lets the system manager change the way <var class="product">Model&nbsp;204</var> processes a particular error or informational message. Changes made to a message affect all users in the Online.
<p><var class="product">Model&nbsp;204</var> handles different message event conditions in different ways. For example:</p>
 
<li>You can use the <var>MSGCTL</var> command to change processing for either standard <var class="product">Model&nbsp;204</var> messages with a <var class="product">Model&nbsp;204</var> prefix or for messages with a user prefix developed by the installation. Note that you can also use the <var>MSGCTL</var> 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 <var class="product">Model&nbsp;204</var> and described in the [[Model 204 installation|Model 204 installation documentation]].</li>
 
<li><var class="product">Model&nbsp;204</var> handles different message event conditions in different ways. For example:
<ul>  
<ul>  
<li>
<li>A message can be displayed on the operator's console.</li>
<p>A message can be displayed on the operator's console.</p>
</li>
   
   
<li>
<li>A message can be displayed on the user's terminal.</li>
<p>A message can be displayed on the user's terminal.</p>
</li>
   
   
<li>
<li>A message can be written to the journal or audit trail data set.</li>
<p>A message can be written to the journal or audit trail data set.</p>
</li>
   
   
<li>
<li>An error can result in the production of a SNAP. </li>
<p>An error can result in the production of a SNAP. </p>
</ul></li>
</li>
 
</ul>
<li>For all <var class="product">Model&nbsp;204</var> message event conditions, the <var class="product">Model&nbsp;204</var> [[M204wiki main page#Messages|message documentation]] lists the error number, the text of the message, and the default action that is taken when the event occurs. </li>
<p>For all <var class="product">Model&nbsp;204</var> message event conditions, the <var class="product">Model&nbsp;204</var> Messages Manual lists the error number, the text of the message, and the default action that is taken when the event occurs. </p>
</ul>
 
====Understanding the NOCOUNT option====
====Understanding the NOCOUNT option====
<p class="note"><b>Note:</b> Rocket Software strongly recommends that you do not change or suppress the COUNT option that is assigned to some messages. The User Language 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 <var class="product">Model&nbsp;204</var> journal, audit trail, or other job output can result in the inability to trace and diagnose problems.</p>
<p class="warn"><b>Attention:</b> Rocket Software strongly recommends that you do not change or suppress the <var>COUNT</var> option that is assigned to some messages. The SOUL compiler depends on using the <var>COUNT</var> 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 <var class="product">Model&nbsp;204</var> journal, audit trail, or other job output can result in the inability to trace and diagnose problems.</p>
 
====How the MSGCTL command can override both the MSGCTL and DEBUGUL parameters====
====How the MSGCTL command can override both the MSGCTL and DEBUGUL parameters====
<p>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 MSGCTL command using the following syntax:</p>
<p>
<p class="code">MSGCTL {M204 | USER}.msg-number TERM
If you use the <var>MSGCTL</var> command, and suppress the display of a message by using the <var>NOTERM</var> keyword, then no matter how the <var>MSGCTL</var> or <var>DEBUGUL</var> parameters are set, the message does not go to the terminal. Conversely, if you want messages displayed at the terminal, enter the <var>MSGCTL</var> command using the following syntax:</p>
<p class="syntax">MSGCTL {M204 | USER}.<span class="term">msg-number</span> TERM
</p>
</p>
====Understanding the NOACTION option====
====Understanding the NOACTION option====
<p>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, <var class="product">Model&nbsp;204</var> resumes the main processing. </p>
<p>
<p class="note"><b>Note:</b> NOACTION has no effect on a restart or a termination message. </p>
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 <var>MSGTL</var>. If a message does not need processing, <var class="product">Model&nbsp;204</var> resumes the main processing. </p>
 
<p class="note"><b>Note:</b> <var>NOACTION</var> has no effect on a restart or a termination message. </p>
 
[[Category: System administrator commands]]
[[Category: System administrator commands]]
[[Category:Commands]]
[[Category:Commands]]

Latest revision as of 19:21, 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:


Option

Action
AUDITAD Puts the specified message on the audit trail as an AD line.
AUDITER Puts the specified message on the audit trail as an ER line.
AUDITMS Puts the specified error message on the audit trail as an MS line.
AUDITRK Puts the specified message on the audit as an RK line.
CAN Causes the message to become a request cancellation message.
COUNT Increments, by one, the message count whenever this message is issued. If the message count exceeds the value of the ERMX parameter, the user's session and processing are stopped.
DUMPALL Dumps the entire Model 204 region. Provides the maximum amount of information for problem determination.
NOACTION Ignores the original option that was assigned the message and returns to main processing.
NOAUDIT Suppresses the auditing of a specific error message. Use with caution, since preventing certain messages from going to the journal could make problem diagnosis more difficult.
NOAUDITAD Puts the specified message on the audit trail as an MS line.
NOAUDITER Puts the specified message on the audit trail as an RK line.
NOAUDITMS Suppresses auditing the specified MS message.
NOAUDITRK Put the specified message on the audit trail as an AD line.
NOAUDITW Suppresses the specified message on Janus Web threads if WEBAUDIT=1. Use with caution, since preventing certain messages from going to the journal could make problem diagnosis more difficult.
NOCOUNT Does not increment, by one, the message count whenever this message is displayed.
NOCTL 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.
NODUMP Does not generate a dump.
NOOPR Does not display the specified message on the operator's console.
NOPREFIX Suppresses the display of the message prefix and number.
NOSAVE Does not save the specified message in the message save table. Note that messages sent to the operator and messages that cause SNAPs are always added to the message save table, regardless of the selection of the SAVE or NOSAVE options.
NOSNAP Suppresses the production of a SNAP when the specified error condition occurs.
NOTERM Does not display the specified message on the user's terminal or for single user jobs in CCAPRINT.

Note: Model 204 passes return codes back in login and logout messages; if you set the NOTERM option for login and logout messages, you cannot get the return code.
NOUP or NOUPPER Reverses the effect of a previous UP option, thus returning the specified message to its original displayed format.
OPR Displays the specified message message on the operator's console.
PREFIX Displays a message prefix (M204 or USER) and message number along with the message.
SAVE Puts a copy of the specified message on the message save table whenever that message is issued. Use the VIEW ERRORS command to examine the saved message.
SNAP SNAP produces the same information as SNAPALL.
SNAPALL The SNAP includes all allocated storage except the Model 204 load module.
SNAPPDL The SNAP includes the registers, module map (alpha and address order), allocated storage map, pushdown list trace, user's server, KOMM, disk buffers containing Model 204 file pages held by the current user (maximum of 4), file directory of current file, and patch information.
SNAPSEL n SNAP includes everything in SNAPPDL as well as other items specified by n. The settings for n can be added together. For example, to output the disk buffers for Tables B and C on a divide-by-zero error:

MSGCTL M204.0554 SNAPSEL 6

Value of n Result
1 Output all Table A and FCT disk buffers for the current file and no CCATEMP disk buffers.
2 Output all Table B disk buffers for the current file and no CCATEMP disk buffers.
4 Output all Table C disk buffers for the current file and no CCATEMP disk buffers.
8 Output all Table D disk buffers for the current file and no CCATEMP disk buffers.
16 Output the disk buffers requested by the previous settings for all files open by this user and no CCATEMP disk buffers. This setting directs the buffer output and coordinates with one of the previous settings.
32 Output all data structures except those which pertain to record locking, resource locking and disk buffers.
64 Output those data structures which pertain to record locking and resource locking.
128 Output all CCATEMP disk buffers and no Model 204 file disk buffers.
TERM Causes the specified message to be displayed on the user's terminal or for single user jobs in CCAPRINT.
UP or UPPER Forces the specified message to be displayed in uppercase.
CLASS
CLASS=P Resets the message so that it is treated as a prompting message. Since you cannot suppress the printing of prompting messages at the terminal, the message is displayed at the APSY user's terminal.

Note: P does not cause a prompt; it only forces the message to appear at the terminal in an APSY.
CLASS=I (informational) Prevents the specified message from being printed at the terminal if the X'02' bit of the MSGCTL parameter is set. Note that this bit is set within an APSY for which informational messages are suppressed.
CLASS=E (error) Prevents the specified message from being printed at the terminal if the X'04' bit of the MSGCTL parameter is set. Note that this bit is set within an APSY for which error messages are suppressed.
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 V7.9 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.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=MSGCTL_command&oldid=120056"