MSIR.1031: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Template:MSIR.1031 skeleton}}
{{Template:MSIR.1031 skeleton}}
<!--Test SOUL.DNC.016.QA in QASHR exercises at least some MSIR.1031 cases. PDS-6626 -->
<p>
<p>
This message can occur if a setText statement doesn't include a variable assignment clause.
A SOUL statement doesn't include a required assignment clause. Possible examples follow:
</p>
</p>
<ul>
<li>A setText statement doesn't include a variable assignment clause. In this case, the following message is produced:
<p class="code>MSIR.1031: SetText must be followed by assignment to target</p></li>
</ul>
<p>
<p>
<b>Response: </b>
<b>Response: </b>
Ensure that the setText statement includes a variable to which the specified text string  will be assigned. This can be a standard variable or longstring, class variable, class property, or a collection member.
Ensure that the SOUL statement includes an appropriate assignment clause.
</p>
</p>
{{Template:MSIR.1031 footer}}
{{Template:MSIR.1031 footer}}

Latest revision as of 19:37, 3 June 2020

MSIR.1031  token must be followed by assignment to target

A SOUL statement doesn't include a required assignment clause. Possible examples follow:

  • A setText statement doesn't include a variable assignment clause. In this case, the following message is produced:

    MSIR.1031: SetText must be followed by assignment to target

Response: Ensure that the SOUL statement includes an appropriate assignment clause.

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