MSIR.1031: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| 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> | ||
A SOUL statement doesn't include a required assignment clause. Possible examples follow: | A SOUL statement doesn't include a required assignment clause. Possible examples follow: | ||
Revision as of 14:44, 21 March 2019
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=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 |