MSIR.0826 NONPRE doesn't make sense for DISALLOW: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Automatically generated page update) |
||
Line 4: | Line 4: | ||
{{Template:MSIR.0826 footer}} | {{Template:MSIR.0826 footer}} | ||
[[Category:MSIR.0800 - MSIR.0999]] |
Latest revision as of 23:35, 3 March 2017
A SIRMETH DISALLOW command was issued with a NONPRE qualifier on a subsystem name. Since non-pre-compiled requests in a subsystem have no privileges to set globals, it doesn't make sense to disallow it.
If the intent was to remove privileges granted to non-pre-compiled requests via a previous SIRMETH ALLOW command, the SIRMETH ALLOW command should be re-issued without the NONPRE keyword, or a SIRMETH ALLOW command should be issued without the NONPRE keyword for the subset of the subsystems for which privileges are to be removed from non-pre-compiled requests.
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 |