MSIR.0571: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
No edit summary
 
Line 1: Line 1:
{{Template:MSIR.0571 skeleton}}
{{Template:MSIR.0571 skeleton}}
<p>
<p>
Description
The <var>[[!DupExit statement|!DupExit]]</var> statement, when used without a macro variable, is not allowed unless the name of the procedure containing <var>!DupExit</var> is <b>shorter</b> than the value of the <var>[[LAUDPROC parameter|LAUDPROC]]</var> parameter.  (As an edge case, a proc whose name is 255 characters long is allowed to have <var>!DupExit</var> if <var>LAUDPROC</var> is 255.)
</p>
</p>
<p>
<p>
<b>Response:</b>
<b>Response:</b> If it makes sense in your application, use a macro variable.  Otherwise, the proc name must be shorter, or the <var>LAUDPROC</var> user 0 parameter must be increased to at least one more than the length of this procedure name (or to 255).
</p>
</p>
{{Template:MSIR.0571 footer}}
{{Template:MSIR.0571 footer}}

Latest revision as of 19:55, 17 April 2019

MSIR.0571  Procname length ​>=​ LAUDPROC for naked !DUPEXIT

The !DupExit statement, when used without a macro variable, is not allowed unless the name of the procedure containing !DupExit is shorter than the value of the LAUDPROC parameter. (As an edge case, a proc whose name is 255 characters long is allowed to have !DupExit if LAUDPROC is 255.)

Response: If it makes sense in your application, use a macro variable. Otherwise, the proc name must be shorter, or the LAUDPROC user 0 parameter must be increased to at least one more than the length of this procedure name (or to 255).

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