MSIR.0457 Subsystem (subsys) not started: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
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 <var class="book">[http://m204wiki.rocketsoftware.com/images/c/c9/SiriNew.pdf Sirius Mods Installation Guide]</var> and is only available to <var class="product">Performance Enhancements V2</var> customers.
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 <var class="book">[[Media:SiriNew.pdf|Sirius Mods Installation Guide]]</var> and is only available to <var class="product">Performance Enhancements V2</var> customers.


[[Category:Sirius Mods messages]] [[Category:MSIR.0400 - MSIR.0599]]
{{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=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

Back to list of messages