MSIR.0422 ALTERNATES not allowed on SIRFIELD (subcmd) command because ERROR format already specified and records have been added to the file: Difference between revisions
Jump to navigation
Jump to search
(Created page with "This message indicates that a SIRFIELD ''''subcmd'''' command was issued with the ALTERNATES clause, and the ERROR format had previously been set for the field. Since records hav...") |
(Automatically generated page update) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
The command is rejected. | The command is rejected. | ||
[[Category: | {{Template:MSIR.0422 footer}} | ||
[[Category:MSIR.0400 - MSIR.0599]] | |||
Latest revision as of 23:12, 3 March 2017
This message indicates that a SIRFIELD 'subcmd' command was issued with the ALTERNATES clause, and the ERROR format had previously been set for the field. Since records have been added to the file, allowing new ALTERNATES could cause previous values matched by ERROR to now be matched by an alternate format, which might change the data, for example when you reorganize the file.
The command is rejected.
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 |