M204.0027 - Revision history

JDamon at 16:59, 8 April 2025

2025-04-08T16:59:13Z

← Older revision		Revision as of 16:59, 8 April 2025
Line 5:		Line 5:
	<li>During Model 204 initialization, if unsupported procs have been stored in CCASYS. Only Rocket supplied procs can be stored in CCASYS.</li>		<li>During Model 204 initialization, if unsupported procs have been stored in CCASYS. Only Rocket supplied procs can be stored in CCASYS.</li>
	<p>or</p>		<p>or</p>
	<li>When the START SUBSYS <i>~~subsysName~~</i> command is issued for a subsystem. During a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. If another user adds a new subsystem procedure between the first procedure file scan and the second, the error can occur.</li>		<li>When the <b><i>START SUBSYS subsysName</i></b> command is issued for a subsystem. During a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. If another user adds a new subsystem procedure between the first procedure file scan and the second, the error can occur.</li>
	</ol>		</ol>

Line 11:		Line 11:
	<ol>		<ol>
	<li>Remove all non-ROCKET procs from CCASYS and restart Model 204.</li>		<li>Remove all non-ROCKET procs from CCASYS and restart Model 204.</li>
	<li>Reissue the START SUBSYS <i>~~subsysName~~</i> command. If this doesn't help, issue the <i>~~'''~~DEBUG SUBSYS subsysName~~'''~~</i> command; the messages produced may provide information pointing to the problem.</LI>		<li>Reissue the <i><b>START SUBSYS subsysName</i></b> command. If this doesn't help, issue the <i><b>DEBUG SUBSYS subsysName</b></i> command; the messages produced may provide information pointing to the problem.</LI>
	</p>		</p>
	{{Template:M204.0027 footer}}		{{Template:M204.0027 footer}}
	<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->		<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->

JDamon at 16:53, 8 April 2025

2025-04-08T16:53:21Z

← Older revision		Revision as of 16:53, 8 April 2025
Line 11:		Line 11:
	<ol>		<ol>
	<li>Remove all non-ROCKET procs from CCASYS and restart Model 204.</li>		<li>Remove all non-ROCKET procs from CCASYS and restart Model 204.</li>
	<li>Reissue the START SUBSYS <i>subsysName</i> command.</LI>		<li>Reissue the START SUBSYS <i>subsysName</i> command. If this doesn't help, issue the <i>'''DEBUG SUBSYS subsysName'''</i> command; the messages produced may provide information pointing to the problem.</LI>
	</p>		</p>
	{{Template:M204.0027 footer}}		{{Template:M204.0027 footer}}
	<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->		<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->

JDamon at 23:28, 7 April 2025

2025-04-07T23:28:31Z

← Older revision		Revision as of 23:28, 7 April 2025
Line 1:		Line 1:
	{{Template:M204.0027 skeleton}}		{{Template:M204.0027 skeleton}}
	<P>~~When~~ Model 204 ~~performs~~ a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. ~~This error occurs when~~ another user adds a new subsystem procedure between the first procedure file scan and the second~~. The~~ error can ~~also~~ occur ~~if unsupported procs have been stored in CCASYS; only Rocket supplied procs can be stored in CCASYS~~.</P>		<P>This error can occur:
	<p><b>Response:</b> Reissue the ~~subsystem~~ command. </p>
			<ol>
			<li>During Model 204 initialization, if unsupported procs have been stored in CCASYS. Only Rocket supplied procs can be stored in CCASYS.</li>
			<p>or</p>
			<li>When the START SUBSYS <i>subsysName</i> command is issued for a subsystem. During a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. If another user adds a new subsystem procedure between the first procedure file scan and the second, the error can occur.</li>
			</ol>

			<p><b>Response:</b>
			<ol>
			<li>Remove all non-ROCKET procs from CCASYS and restart Model 204.</li>
			<li>Reissue the START SUBSYS <i>subsysName</i> command.</LI>
			</p>
	{{Template:M204.0027 footer}}		{{Template:M204.0027 footer}}
	<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->		<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->

JDamon at 22:48, 7 April 2025

2025-04-07T22:48:07Z

← Older revision		Revision as of 22:48, 7 April 2025
Line 1:		Line 1:
	{{Template:M204.0027 skeleton}}		{{Template:M204.0027 skeleton}}
	<P>When Model 204 performs a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. This error occurs when another user adds a new subsystem procedure between the first procedure file scan and the second. The error can also occur if unsupported procs have been ~~store~~ in CCASYS; only Rocket supplied procs can be stored in CCASYS.</P>		<P>When Model 204 performs a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. This error occurs when another user adds a new subsystem procedure between the first procedure file scan and the second. The error can also occur if unsupported procs have been stored in CCASYS; only Rocket supplied procs can be stored in CCASYS.</P>
	<p><b>Response:</b> Reissue the subsystem command. </p>		<p><b>Response:</b> Reissue the subsystem command. </p>
	{{Template:M204.0027 footer}}		{{Template:M204.0027 footer}}
	<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->		<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->

JDamon at 22:27, 7 April 2025

2025-04-07T22:27:18Z

← Older revision		Revision as of 22:27, 7 April 2025
Line 1:		Line 1:
	{{Template:M204.0027 skeleton}}		{{Template:M204.0027 skeleton}}
	<P>When Model 204 performs a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. This error occurs when another user adds a new subsystem procedure between the first procedure file scan and the second. </P>		<P>When Model 204 performs a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. This error occurs when another user adds a new subsystem procedure between the first procedure file scan and the second. The error can also occur if unsupported procs have been store in CCASYS; only Rocket supplied procs can be stored in CCASYS.</P>
	<p><b>Response:</b> Reissue the subsystem command. </p>		<p><b>Response:</b> Reissue the subsystem command. </p>
	{{Template:M204.0027 footer}}		{{Template:M204.0027 footer}}
	<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->		<!-- skeleton as it was in pdf/AUX PROCEDURE DICTIONARY FULL /-->

DmeWiccan: Automatically generated page update

2018-02-13T00:12:34Z

Automatically generated page update

New page

{{Template:M204.0027 skeleton}}
When Model 204 performs a subsystem initialization, the subsystem procedure file is scanned twice. The first scan retrieves the number of subsystem procedures in order to allocate the subsystem's in-core procedure dictionary. The second scan retrieves the procedure information that is copied into the in-core procedure dictionary. This error occurs when another user adds a new subsystem procedure between the first procedure file scan and the second. 
Response: Reissue the subsystem command. 
{{Template:M204.0027 footer}}