M204.0027: Difference between revisions

From m204wiki
Jump to navigation Jump to search
JDamon (talk | contribs)
No edit summary
JDamon (talk | contribs)
No edit summary
 
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 /-->

Latest revision as of 16:59, 8 April 2025

M204.0027  Aux procedure dictionary full

This error can occur:

  1. During Model 204 initialization, if unsupported procs have been stored in CCASYS. Only Rocket supplied procs can be stored in CCASYS.
  2. or

  3. When the START SUBSYS subsysName 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.

Response:

  1. Remove all non-ROCKET procs from CCASYS and restart Model 204.
  2. Reissue the START SUBSYS subsysName command. If this doesn't help, issue the DEBUG SUBSYS subsysName command; the messages produced may provide information pointing to the problem.
  3. 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