MSIR.0793 Inconsistent (what) in class header: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
Line 3: Line 3:
Likely causes of this are typos in the class name or <var>RequiredSuffix</var> value. One way to avoid the latter problem is to simply not specify the <var>RequiredSuffix</var> parameter on any but the first class block for the class &#x2014; that is the only place it is required.
Likely causes of this are typos in the class name or <var>RequiredSuffix</var> value. One way to avoid the latter problem is to simply not specify the <var>RequiredSuffix</var> parameter on any but the first class block for the class &#x2014; that is the only place it is required.


{{Template:MSIR.0793 footer}}
[[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]]
[[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]]

Revision as of 21:59, 11 July 2016

A Class statement for a previously declared class had an attribute inconsistent with a previous declaration. Currently, this message is only used for the RequiredSuffix parameter, so it indicates that the required suffix specified in the class definition continuation did not match that on the original definition.

Likely causes of this are typos in the class name or RequiredSuffix value. One way to avoid the latter problem is to simply not specify the RequiredSuffix parameter on any but the first class block for the class — that is the only place it is required.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter
ECHODisplays the line that caused the error

Back to list of messages