JAL: minor formatting

2018-03-20T21:19:09Z

minor formatting

← Older revision		Revision as of 21:19, 20 March 2018
Line 3:		Line 3:
	<P>		<P>
	This error usually occurs with a <var>Store Record</var> statement that references more than 127 subscripted values in a SOUL array. An internal table of 512 bytes is allocated by the SOUL compiler to hold		This error usually occurs with a <var>Store Record</var> statement that references more than 127 subscripted values in a SOUL array. An internal table of 512 bytes is allocated by the SOUL compiler to hold
	temporary variables. This table consists of one fullword counter and 127 fullwords of data. Each of those 127 fullwords represents a temporary variable. This change in the handling of temporary variables improves performance and reduces space		temporary variables. This table consists of one fullword counter and 127 fullwords of data. Each of those 127 fullwords represents a temporary variable. This change in the handling of temporary variables improves performance and reduces space requirements in VTBL and STBL.</P>
	requirements in VTBL and STBL.</P>		<p>This error could also occur with a <var>Print</var> statement in Model 204 version 7.4 or, less likely, with a <var>Find</var>, <var>Audit</var>, or <var>Update Record</var> statement.</p>
	<p>This error could also occur with a <var>Print</var> statement in Model 204 version 7.4 or, less likely, with a <var>Find</var>, <var>Audit</var>, or <var>Update ~~record~~</var> statement.</p>
	<p>		<p>
	<b>Response:</b></p>		<b>Response:</b></p>
Line 39:		Line 38:
	END FIND</p>		END FIND</p>

	<p><var>Update Record</var>: Break up the statement into multiple parts, similar to the <var>Store Record</var> example.</p>		<p>
	<p><var>Audit</var>: Break up the Audit into multiple Audit statements, each having a limit of 127 variable array references.</p>		<var>Update Record</var>: Break up the statement into multiple parts, similar to the <var>Store Record</var> example.</p>
	<p><var>Print</var>: The issue has been resolved in SirMods 8.1. Therefore, the best solution for Model 204 version 7.4 is to rerun the job with a load module that includes SirMods 8.1 linked in. As of Model 204 version 7.5, SirMods is totally integrated into the Model 204 nucleus, so no special linking is required.</p>		<p>
			<var>Audit</var>: Break up the Audit into multiple Audit statements, each having a limit of 127 variable array references.</p>
			<p>
			<var>Print</var>: The issue has been resolved in SirMods 8.1. Therefore, the best solution for Model 204 version 7.4 is to rerun the job with a load module that includes SirMods 8.1 linked in. As of Model 204 version 7.5, SirMods is totally integrated into the Model 204 nucleus, so no special linking is required.
			</p>
	{{Template:M204.2840 footer}}		{{Template:M204.2840 footer}}
	<!-- skeleton as it was in pdf/STATEMENT HAS TOO MANY INTERMEDIATE RESULTS/-->		<!-- skeleton as it was in pdf/STATEMENT HAS TOO MANY INTERMEDIATE RESULTS/-->

DmeWiccan: Automatically generated page update

2018-03-13T18:02:22Z

Automatically generated page update

New page

{{Template:M204.2840 skeleton}}


This error usually occurs with a <var>Store Record</var> statement that references more than 127 subscripted values in a SOUL array. An internal table of 512 bytes is allocated by the SOUL compiler to hold
temporary variables. This table consists of one fullword counter and 127 fullwords of data. Each of those 127 fullwords represents a temporary variable. This change in the handling of temporary variables improves performance and reduces space
requirements in VTBL and STBL.
This error could also occur with a <var>Print</var> statement in Model 204 version 7.4 or, less likely, with a <var>Find</var>, <var>Audit</var>, or <var>Update record</var> statement.

Response:

<var>Store Record</var>: Break up the statement into multiple parts as in the following example: 
STORE:
STORE RECORD
FIELDX = %ARRAY(1)
FIELDX = %ARRAY(2)
...
FIELDX = %ARRAY(127)
END STORE
FRN IN STORE
FOR %X FROM 128 TO 999
ADD FIELDX = %ARRAY(%X)
END FOR
END FOR
etc. 

<var>Find</var>: Break up the statement into multiple parts as in the following example:
FD1:
IN filename FD
FIELDX = %ARRAY(1)
FIELDX = %ARRAY(2)
…..
FIELDX = %ARRAY(127)
END FIND
..
FD2:
FD IN FD1
FIELDX = %ARRAY(128)
……
END FIND

<var>Update Record</var>: Break up the statement into multiple parts, similar to the <var>Store Record</var> example.
<var>Audit</var>: Break up the Audit into multiple Audit statements, each having a limit of 127 variable array references.
<var>Print</var>: The issue has been resolved in SirMods 8.1. Therefore, the best solution for Model 204 version 7.4 is to rerun the job with a load module that includes SirMods 8.1 linked in. As of Model 204 version 7.5, SirMods is totally integrated into the Model 204 nucleus, so no special linking is required.

{{Template:M204.2840 footer}}

M204.2840 - Revision history

JAL: minor formatting

DmeWiccan: Automatically generated page update