M204.0473 - Revision history

JDamon at 17:13, 8 April 2025

2025-04-08T17:13:04Z

← Older revision		Revision as of 17:13, 8 April 2025
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.

JDamon at 22:46, 7 April 2025

2025-04-07T22:46:07Z

← Older revision		Revision as of 22:46, 7 April 2025
Line 3:		Line 3:
	<LI>If the message reports a specific subsystem name, that subsystem could not be initialized because of an error.</LI>		<LI>If the message reports a specific subsystem name, that subsystem could not be initialized because of an error.</LI>

	<LI>If the message is issued by User 0 during Model 204 initialization and it reports <code>SUBSYSTEMS</code>, APSY initialization failed, and ~~<var class="term">subsysName</var>~~ will not be available during this run.</LI>		<LI>If the message is issued by User 0 during Model 204 initialization and it reports <code>SUBSYSTEMS</code>, APSY initialization failed, and APSY subsystems will not be available during this run. Otherwise, <code>subsysName</code> has failed to initialize.</LI>

	<LI>If this message is preceded by the following message, then the user attempted to start a suspended subsystem:		<LI>If this message is preceded by the following message, then the user attempted to start a suspended subsystem:
Line 15:		Line 15:
	<b>System manager response:</b> If the message reports a specific subsystem, look at the audit trail or issue the <var>TEST</var> subsystem command to determine which error caused subsystem initialization to fail.</P>		<b>System manager response:</b> If the message reports a specific subsystem, look at the audit trail or issue the <var>TEST</var> subsystem command to determine which error caused subsystem initialization to fail.</P>
	<P>		<P>
	If the message reports <code>SUBSYSTEMS</code>, the ~~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.		If the message reports <code>SUBSYSTEMS</code>, there are two possible causes:</p>
	</P>		<ol>
			<li>[[M204.0027]] was issued indicating that the CCASYS auxiliary procedure dictionary was full</P></li>
			<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>
			</ol>
	{{Template:M204.0473 footer}}		{{Template:M204.0473 footer}}
	<!-- skeleton as it was in pdf/UNABLE TO INITIALIZE [subsystem name \| SUBSYSTEMS]/-->		<!-- skeleton as it was in pdf/UNABLE TO INITIALIZE [subsystem name \| SUBSYSTEMS]/-->

JAL: misc formatting

2018-02-26T20:43:24Z

misc formatting

← Older revision		Revision as of 20:43, 26 February 2018
Line 5:		Line 5:
	<LI>If the message is issued by User 0 during Model 204 initialization and it reports <code>SUBSYSTEMS</code>, APSY initialization failed, and <var class="term">subsysName</var> will not be available during this run.</LI>		<LI>If the message is issued by User 0 during Model 204 initialization and it reports <code>SUBSYSTEMS</code>, APSY initialization failed, and <var class="term">subsysName</var> will not be available during this run.</LI>

	<LI>If this message is preceded by the following message, then the user attempted to start a suspended subsystem:~~</LI>~~		<LI>If this message is preceded by the following message, then the user attempted to start a suspended subsystem:
	~~</ul>~~
	<p class="code">M204.2661: SUBSYSTEM <i>name</i> SUSPENDED</p>		<p class="code">M204.2661: SUBSYSTEM <i>name</i> SUSPENDED</p>
	<P>		<P>
	The user must issue the <var>RESUME SUBSYSTEM</var> command to make the subsystem available for use.</P>		The user must issue the <var>RESUME SUBSYSTEM</var> command to make the subsystem available for use.</P></li>
			</ul>
	<P>		<P>
	<b>Response:</b> Notify the system manager.</P>		<b>Response:</b> Notify the system manager.</P>
Line 15:		Line 15:
	<b>System manager response:</b> If the message reports a specific subsystem, look at the audit trail or issue the <var>TEST</var> subsystem command to determine which error caused subsystem initialization to fail.</P>		<b>System manager response:</b> If the message reports a specific subsystem, look at the audit trail or issue the <var>TEST</var> subsystem command to determine which error caused subsystem initialization to fail.</P>
	<P>		<P>
	If the message reports <code>SUBSYSTEMS</code>, the 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.</P>		If the message reports <code>SUBSYSTEMS</code>, the 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.
			</P>
	{{Template:M204.0473 footer}}		{{Template:M204.0473 footer}}
	<!-- skeleton as it was in pdf/UNABLE TO INITIALIZE [subsystem name \| SUBSYSTEMS]/-->		<!-- skeleton as it was in pdf/UNABLE TO INITIALIZE [subsystem name \| SUBSYSTEMS]/-->

DmeWiccan: Automatically generated page update

2018-02-23T03:24:42Z

Automatically generated page update

New page

{{Template:M204.0473 skeleton}}
<ul>
<LI>If the message reports a specific subsystem name, that subsystem could not be initialized because of an error.</LI>

<LI>If the message is issued by User 0 during Model 204 initialization and it reports <code>SUBSYSTEMS</code>, APSY initialization failed, and <var class="term">subsysName</var> will not be available during this run.</LI>

<LI>If this message is preceded by the following message, then the user attempted to start a suspended subsystem:</LI>
</ul>
M204.2661: SUBSYSTEM name SUSPENDED

The user must issue the <var>RESUME SUBSYSTEM</var> 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 <var>TEST</var> subsystem command to determine which error caused subsystem initialization to fail.

If the message reports <code>SUBSYSTEMS</code>, the 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.
{{Template:M204.0473 footer}}