MSIR.0706 Subsystem (subsys) not quiesced within (nsec) seconds: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
A <tt>SIRFACT QUIESCE</tt> command was issued but the subsystem did not quiesce within the implicit or explicit WAIT time. Either re-issue the command, perhaps with a higher WAIT time (the default is 3 seconds) or with the BUMP parameter. The most likely cause of this problem is a user on a screen in the middle of a compilation, probably with a bunch of compiler messages on the screen.
A <tt>SIRFACT QUIESCE</tt> command was issued but the subsystem did not quiesce within the implicit or explicit WAIT time. Either re-issue the command, perhaps with a higher WAIT time (the default is 3 seconds) or with the BUMP parameter. The most likely cause of this problem is a user on a screen in the middle of a compilation, probably with a bunch of compiler messages on the screen.


[[Category:Sirius Mods messages]] [[Category:MSIR.0600 - MSIR.0799]]
{{Template:MSIR.0706 footer}}
[[Category:MSIR.0600 - MSIR.0799]]

Latest revision as of 23:33, 3 March 2017

A SIRFACT QUIESCE command was issued but the subsystem did not quiesce within the implicit or explicit WAIT time. Either re-issue the command, perhaps with a higher WAIT time (the default is 3 seconds) or with the BUMP parameter. The most likely cause of this problem is a user on a screen in the middle of a compilation, probably with a bunch of compiler messages on the screen.


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