M204.0473: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 17: | Line 17: | ||
If the message reports <code>SUBSYSTEMS</code>, there are two possible causes:</p> | If the message reports <code>SUBSYSTEMS</code>, there are two possible causes:</p> | ||
<ol> | <ol> | ||
<li>[[M204.0027]] was issued indicating that the CCASYS auxiliary procedure dictionary was full</P></li> | <li>[[M204.0027]] was issued indicating that CCASYS contained non-Rocket supported procs or the CCASYS auxiliary procedure dictionary was full</P></li> | ||
<P>or</p> | <P>or</p> | ||
<li>Server tables for User 0 are not large enough to initialize subsystem handling. Change the User 0 parameters so that its server table sizes are at least as large as the sizes listed in the description of message [[M204.1457]], and then restart Model 204. | <li>Server tables for User 0 are not large enough to initialize subsystem handling. Change the User 0 parameters so that its server table sizes are at least as large as the sizes listed in the description of message [[M204.1457]], and then restart Model 204. |
Latest revision as of 17:13, 8 April 2025
M204.0473 Unable to initialize subsysName
- If the message reports a specific subsystem name, that subsystem could not be initialized because of an error.
- If the message is issued by User 0 during Model 204 initialization and it reports
SUBSYSTEMS
, APSY initialization failed, and APSY subsystems will not be available during this run. Otherwise,subsysName
has failed to initialize. - If this message is preceded by the following message, then the user attempted to start a suspended subsystem:
M204.2661: SUBSYSTEM name SUSPENDED
The user must issue the RESUME SUBSYSTEM command to make the subsystem available for use.
Response: Notify the system manager.
System manager response: If the message reports a specific subsystem, look at the audit trail or issue the TEST subsystem command to determine which error caused subsystem initialization to fail.
If the message reports SUBSYSTEMS
, there are two possible causes:
- M204.0027 was issued indicating that CCASYS contained non-Rocket supported procs or the CCASYS auxiliary procedure dictionary was full
- Server tables for User 0 are not large enough to initialize subsystem handling. Change the User 0 parameters so that its server table sizes are at least as large as the sizes listed in the description of message M204.1457, and then restart Model 204.
or
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 |