MSIR.0457 Subsystem (subsys) not started: Difference between revisions
Jump to navigation
Jump to search
m (link repair) |
(Automatically generated page update) |
||
Line 2: | Line 2: | ||
{{Template:MSIR.0457 footer}} | {{Template:MSIR.0457 footer}} | ||
[[Category:MSIR.0400 - MSIR.0599]] |
Latest revision as of 23:13, 3 March 2017
The SIRAPSY command was issued against subsystem subsys which was not START'ed. SIRAPSY can only be issued against START'ed subsystems. Either correct the spelling of subsys, or START the subsystem and then issue the SIRAPSY command. If the SIRAPSY command is to be regularly issued for subsys, the appropriate SIRAPSY commands for the subsystem can be put in the job stream that START's the subsystem, a proc that contains the START command for the subsystem or even in the subsystem's initialization procedure. The SIRAPSY command is documented in the Sirius Mods Installation Guide and is only available to Performance Enhancements V2 customers.
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 |