M204.2474 - Revision history

JAL: remove 0 from token0

2018-03-26T22:21:01Z

remove 0 from token0

← Older revision		Revision as of 22:21, 26 March 2018
Line 5:		Line 5:
	at compile time, the request is not evaluated. </P>		at compile time, the request is not evaluated. </P>
	<ul>		<ul>
	<li><var class="term">~~token0~~</var> is the name of the routine that detected the problem:		<li><var class="term">token</var> is the name of the routine that detected the problem:
	<ul>		<ul>
	<li>GLBFDCHK: Checks a single global object.</li>		<li>GLBFDCHK: Checks a single global object.</li>

JAL: change to lc

2018-03-19T20:44:56Z

change to lc

← Older revision		Revision as of 20:44, 19 March 2018
Line 2:		Line 2:

	<P>		<P>
	This is an information message that describes a bad or incomplete ~~GLOBAL~~ variable that was found. Usually the message describes an incomplete ~~GLOBAL~~ variable, which reflects an incomplete request. If this message occurs		This is an information message that describes a bad or incomplete global variable that was found. Usually the message describes an incomplete global variable, which reflects an incomplete request. If this message occurs
	at compile time, the request is not evaluated. </P>		at compile time, the request is not evaluated. </P>
	<ul>		<ul>
Line 45:		Line 45:
	<li><var class="term">hexValue0</var> is the GTBL offset of the header of the variable with the problem.</li>		<li><var class="term">hexValue0</var> is the GTBL offset of the header of the variable with the problem.</li>

	<li><var class="term">hexValue2</var> is the header and the first 8 bytes of the variable with the problem.</li>		<li><var class="term">hexValue2</var> is the header and the first eight bytes of the variable with the problem.</li>
	</ul>		</ul>
	<p>		<p>
	<b>Response:</b> The message that immediately preceded message M204.2474 identifies the problem that caused Model 204 to issue this message. If the preceding message does not give you enough information to resolve the problem yourself,		<b>Response:</b> The message that immediately preceded message M204.2474 identifies the problem that caused Model 204 to issue this message. If the preceding message does not give you enough information to resolve the problem yourself,
	retain the audit trail and contact [[Contacting Rocket Software Technical Support\|Technical Support]]. If Rocket Software requests more complete diagnostic information, the <var>MSGCTL</var> command can set this message to snap.</p>		retain the audit trail and contact [[Contacting Rocket Software Technical Support\|Technical Support]]. If Rocket Software requests more complete diagnostic information, the <var>MSGCTL</var> command can set this message to snap.
			</p>
	{{Template:M204.2474 footer}}		{{Template:M204.2474 footer}}
	<!-- skeleton as it was in pdf/routine_name BAD GLOBAL VARIABLE: gtbl_section var_type -error_description gtbl_offset global_object/-->		<!-- skeleton as it was in pdf/routine_name BAD GLOBAL VARIABLE: gtbl_section var_type -error_description gtbl_offset global_object/-->

DmeWiccan: Automatically generated page update

2018-03-14T03:46:50Z

Automatically generated page update

New page

{{Template:M204.2474 skeleton}}


This is an information message that describes a bad or incomplete GLOBAL variable that was found. Usually the message describes an incomplete GLOBAL variable, which reflects an incomplete request. If this message occurs
at compile time, the request is not evaluated. 
<ul>
<li><var class="term">token0</var> is the name of the routine that detected the problem:
<ul>
<li>GLBFDCHK: Checks a single global object.</li>
<li>GLBCHECK: Checks all global objects after an error has occurred.</li>
</ul></li>

<li><var class="term">token2</var> is the section of GTBL where the problem was found:
<ul>
<li>TEMP IMAGE/SCREEN/MENU SECTION</li>
<li>PERM IMAGE/SCREEN/MENU SECTION</li>
<li>LIST/FOUNDSET/SORTSET SECTION</li>
<li>TEMP POSITION SECTION</li>
<li>PERM POSITION SECTION</li>
</ul></li>

<li><var class="term">token3</var> is the type of variable that had the problem:
<ul>
<li>YVAR....: Image.</li>
<li>ZVAR....: Screen or menu.</li>
<li>XVAR....: List or foundset.</li>
<li>GVAR....: Group list or foundset.</li>
<li>GXVAR...: Individual file from a group list or foundset.</li>
<li>SVAR....: Sorted record set.</li>
<li>PSVAR...: Remembered position.</li>
</ul></li>

<li><var class="term">token4</var> describes the nature of the error:
<ul>
<li>GLOBAL VARIABLE NOT SET UP</li>
<li>ACTUAL VS. EXPECTED GLTYPE MISMATCH</li>
<li>ACTUAL VS. EXPECTED VTYPE MISMATCH</li>
<li>INVALID GLOBAL TYPE FOR THIS GTBL SECTION</li>
<li>NO RECORD ENQUEUING ENTRY</li>
<li>NO SVAR PAGE CHAIN</li>
<li>INVALID VTYPE FOR THIS GLOBAL TYPE</li>
<li>INVALID VARIABLE LENGTH</li>
</ul></li>

<li><var class="term">hexValue0</var> is the GTBL offset of the header of the variable with the problem.</li>

<li><var class="term">hexValue2</var> is the header and the first 8 bytes of the variable with the problem.</li>
</ul>

Response: The message that immediately preceded message M204.2474 identifies the problem that caused Model 204 to issue this message. If the preceding message does not give you enough information to resolve the problem yourself,
retain the audit trail and contact [[Contacting Rocket Software Technical Support|Technical Support]]. If Rocket Software requests more complete diagnostic information, the <var>MSGCTL</var> command can set this message to snap.
{{Template:M204.2474 footer}}