MSIR.0970: Difference between revisions
Jump to navigation
Jump to search
EllieWiccan (talk | contribs) (Automatically generated page update) |
No edit summary |
||
(5 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Template:MSIR.0970 skeleton}} | {{Template:MSIR.0970 skeleton}} | ||
<p> | <p> | ||
A SOUL statement that includes a directive had been coded incorrectly. The following examples relate to use of the tilda directive within targeted text statements ( audittext, printtext, and tracetext ), which is the only directive for which this message would currently be produced : | |||
</p> | </p> | ||
<ul> | |||
<li>A ~ directive has been coded without a following target expression, enclosed in curly braces, on the same line, in which case the following message is produced: | |||
<p class="code>MSIR.0970: Invalid use of '~' directive: must be followed by expression on same line</p></li> | |||
<li>The target of a ~ directive is an expression including another ~, making the directive unresovable, leading to: | |||
<p class="code>MSIR.0970: Invalid use of '~' directive: must be followed by non-'~' expression</p></li> | |||
<li>A ~ directive has been coded that isn't currently supported, the currently supported directives being ~exprE, ~exprS, ~noCont, ~noEll, ~noExpr, and ~raw. This produces the message: | |||
<p class="code>MSIR.0970: Invalid use of '~' directive: unsupported directive 'nnnn'</p></li> | |||
<li>A ~ directive must be coded following the ~ character, and within curly brackets, otherwise the followig message may be produced: | |||
<p class="code>MSIR.0970: Invalid use of '~' directive: invalid directive qualifier 'nnnn'</p></li> | |||
</ul> | |||
<p> | <p> | ||
<b>Response:</b> | <b>Response:</b> | ||
</p> | </p> | ||
{{Template:MSIR.0970 footer}} | {{Template:MSIR.0970 footer}} |
Latest revision as of 10:01, 25 April 2019
MSIR.0970 Invalid use of 'token' directive: token2
A SOUL statement that includes a directive had been coded incorrectly. The following examples relate to use of the tilda directive within targeted text statements ( audittext, printtext, and tracetext ), which is the only directive for which this message would currently be produced :
- A ~ directive has been coded without a following target expression, enclosed in curly braces, on the same line, in which case the following message is produced:
MSIR.0970: Invalid use of '~' directive: must be followed by expression on same line
- The target of a ~ directive is an expression including another ~, making the directive unresovable, leading to:
MSIR.0970: Invalid use of '~' directive: must be followed by non-'~' expression
- A ~ directive has been coded that isn't currently supported, the currently supported directives being ~exprE, ~exprS, ~noCont, ~noEll, ~noExpr, and ~raw. This produces the message:
MSIR.0970: Invalid use of '~' directive: unsupported directive 'nnnn'
- A ~ directive must be coded following the ~ character, and within curly brackets, otherwise the followig message may be produced:
MSIR.0970: Invalid use of '~' directive: invalid directive qualifier 'nnnn'
Response:
Message attributes:
RETCODEO=0 | Sets online return code |
---|---|
RETCODEB=4 | Sets batch (single user) return code |
CLASS=E | Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter |
AUDITER | Writes the message with line type ER to the audit trail |
COUNT | Increments the error count (ERCNT) parameter |
ECHO | Displays the line that caused the error |