HLI: Model 204 tables - Revision history

ELowell: /* Overview */

2016-07-15T23:21:32Z

Overview

← Older revision		Revision as of 23:21, 15 July 2016
Line 8:		Line 8:
	See [[Large request considerations]] for more information about user work areas. </p>		See [[Large request considerations]] for more information about user work areas. </p>
	<p>		<p>
	~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var>~~ for a description of individual HLI calls. </p>		See [[HLI: Function summary]] for a description of individual HLI calls. </p>

	==User work area==		==User work area==

ELowell: /* Specifying user table size */

2016-07-15T23:20:50Z

Specifying user table size

← Older revision		Revision as of 23:20, 15 July 2016
Line 89:		Line 89:
	</table>		</table>
	<p>		<p>
	~~Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var>~~ for information about IFAM1, IFAM2, and IFAM4 jobs ~~and~~ for a description of the IFUTBL call.</p>		See [[HLI: Job design factors]] for information about IFAM1, IFAM2, and IFAM4 jobs. See <var>[[IFUTBL (HLI function)\|IFUTBL]]</var> for a description of the IFUTBL call.</p>

	<p class="note"><b>Note:</b> In IFAM1, IFAM2, and IFAM4, the Model 204 server area must be large enough to accommodate the aggregate work area table size for HLI threads in the job. </p>		<p class="note"><b>Note:</b> In IFAM1, IFAM2, and IFAM4, the Model 204 server area must be large enough to accommodate the aggregate work area table size for HLI threads in the job. </p>

ELowell: /* Avoiding table full conditions */

2016-07-15T23:16:20Z

Avoiding table full conditions

← Older revision		Revision as of 23:16, 15 July 2016
Line 107:		Line 107:
	However, you might encounter a table full condition for a noncompiled call when the table is already full of entries for calls issued by the thread. If a table is full, Model 204 returns a completion code of 7 to the HLI program. </p>		However, you might encounter a table full condition for a noncompiled call when the table is already full of entries for calls issued by the thread. If a table is full, Model 204 returns a completion code of 7 to the HLI program. </p>
	<p>		<p>
	To avoid table full conditions, when a compilation is no longer needed, delete it with a call to ~~IFFLUSH. Refer to the~~ <var ~~class="book"~~>~~Rocket Model 204 Host Language Interface Reference Manual~~</var> ~~for a description of the IFFLUSH call~~. </p>		To avoid table full conditions, when a compilation is no longer needed, delete it with a call to <var>[[IFFLUSH (HLI function)\|IFFLUSH]]</var>.</p>

	==File group table (FTBL)==		==File group table (FTBL)==

JAL: typo

2016-07-05T21:34:17Z

typo

← Older revision		Revision as of 21:34, 5 July 2016
Line 224:		Line 224:
	<p>		<p>
	These statements require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evaluation, and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL are released after the <var>Find</var> is evaluated. </p></li>		These statements require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evaluation, and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL are released after the <var>Find</var> is evaluated. </p></li>
			</ul>

	==Compiler variable table (VTBL)==		==Compiler variable table (VTBL)==

JDamon: removed the bullet on Full Screen editor - doesn't apply when using HLI

2016-05-11T21:58:18Z

removed the bullet on Full Screen editor - doesn't apply when using HLI

← Older revision		Revision as of 21:58, 11 May 2016
Line 224:		Line 224:
	<p>		<p>
	These statements require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evaluation, and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL are released after the <var>Find</var> is evaluated. </p></li>		These statements require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evaluation, and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL are released after the <var>Find</var> is evaluated. </p></li>

	~~<li>The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages, and each CCATEMP page allocated is tracked in TTBL.</li>~~
	~~</ul>~~

	==Compiler variable table (VTBL)==		==Compiler variable table (VTBL)==

JDamon: Evalulation was misspelled

2016-05-11T21:15:19Z

Evalulation was misspelled

← Older revision		Revision as of 21:15, 11 May 2016
Line 223:		Line 223:
	<li>Various <var>Find</var> statements. Most prominently, <var>IFFIND</var> calls, direct searches, including <code>IS PRESENT</code>, and range retrievals using the Ordered Index.		<li>Various <var>Find</var> statements. Most prominently, <var>IFFIND</var> calls, direct searches, including <code>IS PRESENT</code>, and range retrievals using the Ordered Index.
	<p>		<p>
	These statements require some number of CCATEMP pages (depending on the complexity of the selection criteria) for ~~evalulation~~, and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL are released after the <var>Find</var> is evaluated. </p></li>		These statements require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evaluation, and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL are released after the <var>Find</var> is evaluated. </p></li>

	<li>The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages, and each CCATEMP page allocated is tracked in TTBL.</li>		<li>The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages, and each CCATEMP page allocated is tracked in TTBL.</li>

JAL: minor formatting

2016-05-10T22:51:08Z

minor formatting

← Older revision		Revision as of 22:51, 10 May 2016
Line 88:		Line 88:
	</tr>		</tr>
	</table>		</table>
	<p>Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for information about IFAM1, IFAM2, and IFAM4 jobs and for a description of the IFUTBL call.</p>		<p>
			Refer to the <var class="book">Rocket Model 204 Host Language Interface Reference Manual</var> for information about IFAM1, IFAM2, and IFAM4 jobs and for a description of the IFUTBL call.</p>

	<p class="note"><b>Note:</b> In IFAM1, IFAM2, and IFAM4, the Model 204 server area must be large enough to accommodate the aggregate work area table size for HLI threads in the job. </p>		<p class="note"><b>Note:</b> In IFAM1, IFAM2, and IFAM4, the Model 204 server area must be large enough to accommodate the aggregate work area table size for HLI threads in the job. </p>
Line 165:		Line 166:
	<li>		<li>
	Each IFGET compilation generates 12 bytes of control information. Additionally, each field name takes 16 bytes.		Each IFGET compilation generates 12 bytes of control information. Additionally, each field name takes 16 bytes.
	<p>Additional bytes in QTBL are used by IFFTCH, IFUPDT, IFGET, and IFPUT as necessary based on the following storage requirements: </p>		<p>
			Additional bytes in QTBL are used by IFFTCH, IFUPDT, IFGET, and IFPUT as necessary based on the following storage requirements: </p>
	<ul>		<ul>
	<li>If a field name list is specified, each field name or field name variable in the list takes 8 bytes. </li>		<li>If a field name list is specified, each field name or field name variable in the list takes 8 bytes. </li>
Line 217:		Line 219:
	==Temporary work table (TTBL)==		==Temporary work table (TTBL)==
	<p>		<p>
	TTBL is a collection of 4-byte CCATEMP page numbers currently in use by each user. Those entries point to CCATEMP pages that have been allocated by:		TTBL is a collection of 4-byte CCATEMP page numbers currently in use by each user. Those entries point to CCATEMP pages that have been allocated by: </p>
	<li>		<ul>
	Various ~~FIND~~ statements. Most prominently, IFFIND calls, direct searches, including IS PRESENT, and range retrievals using the ~~ordered index~~. These statements ~~all~~ require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evalulation and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL, are released after the ~~FIND has been~~ evaluated.		<li>Various <var>Find</var> statements. Most prominently, <var>IFFIND</var> calls, direct searches, including <code>IS PRESENT</code>, and range retrievals using the Ordered Index.
	</li>		<p>
	<li>		These statements require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evalulation, and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL are released after the <var>Find</var> is evaluated. </p></li>
	The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages and each CCATEMP page allocated is tracked in TTBL.
	</li>		<li>The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages, and each CCATEMP page allocated is tracked in TTBL.</li>
			</ul>

	==Compiler variable table (VTBL)==		==Compiler variable table (VTBL)==
Line 236:		Line 239:
	<ul>		<ul>
	<li>IFCOUNT allocates one 8-byte entry. </li>		<li>IFCOUNT allocates one 8-byte entry. </li>
	<li>On a single cursor IFSTRT thread, each IFFIND allocates one basic entry, either 8 bytes for a single file or (8 + 8*<var class="term">number-of-files</var>) bytes for a group. On a multiple cursor IFSTRT thread, each compiled IFFIND generates one basic entry for a single file or group.		<li>On a single cursor IFSTRT thread, each IFFIND allocates one basic entry, either 8 bytes for a single file or <code>(8 + 8*<var class="term">number-of-files</var>)</code> bytes for a group. On a multiple cursor IFSTRT thread, each compiled IFFIND generates one basic entry for a single file or group.

	<p>In addition to the basic entry, IFFIND allocates additional bytes in VTBL as listed below. Model 204 releases all but the basic entry after evaluating the IFFIND call.</p>		<p>In addition to the basic entry, IFFIND allocates additional bytes in VTBL as listed below. Model 204 releases all but the basic entry after evaluating the IFFIND call.</p>
Line 293:		Line 296:
	HLI calls that specify lists and %variables use space in VTBL as follows: </p>		HLI calls that specify lists and %variables use space in VTBL as follows: </p>
	<ul>		<ul>
	<li>Each list allocates an entry, either 8 bytes for a single file or (8+8*<var class="term">number-of-files</var>) bytes for a group.</li>		<li>Each list allocates an entry, either 8 bytes for a single file or <code>(8+8*<var class="term">number-of-files</var>)</code> bytes for a group.</li>
	<li>Each %variable allocates one 28-byte entry. </li>		<li>Each %variable allocates one 28-byte entry. </li>
	</ul>		</ul>

JDamon: Backpaging facility no longer uses TTBL - uses BKPGLIST pointed to by KWPBKPG

2016-05-10T20:00:08Z

Backpaging facility no longer uses TTBL - uses BKPGLIST pointed to by KWPBKPG

← Older revision		Revision as of 20:00, 10 May 2016
Line 223:		Line 223:
	<li>		<li>
	The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages and each CCATEMP page allocated is tracked in TTBL.		The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages and each CCATEMP page allocated is tracked in TTBL.
	~~</li>~~
	~~<li>~~
	~~The backpaging facility. If NBKPG > 0, then each user will potentially have NBKPG entries in TTBL to track backpage images for that user.~~
	</li>		</li>

JDamon: More complete description of entries in TTBL

2016-05-10T19:22:49Z

More complete description of entries in TTBL

← Older revision		Revision as of 19:22, 10 May 2016
Line 217:		Line 217:
	==Temporary work table (TTBL)==		==Temporary work table (TTBL)==
	<p>		<p>
	~~IFFIND uses~~ TTBL entries to ~~keep track of temporary storage~~. ~~The~~ number of ~~TTBL entries required depends~~ on the complexity of the selection criteria. ~~Model 204 deletes~~ TTBL ~~entries as soon as~~ the ~~IFFIND~~ has been ~~executed~~. </p>		TTBL is a collection of 4-byte CCATEMP page numbers currently in use by each user. Those entries point to CCATEMP pages that have been allocated by:
	<p>		<li>
	TTBL entries ~~are 4 bytes each~~. </p>		Various FIND statements. Most prominently, IFFIND calls, direct searches, including IS PRESENT, and range retrievals using the ordered index. These statements all require some number of CCATEMP pages (depending on the complexity of the selection criteria) for evalulation and each CCATEMP page allocated is tracked by an entry in TTBL. These CCATEMP pages and their corresponding entries in TTBL, are released after the FIND has been evaluated.
			</li>
			<li>
			The full screen editor. When a procedure is being edited, the procedure is copied into CCATEMP pages and each CCATEMP page allocated is tracked in TTBL.
			</li>
			<li>
			The backpaging facility. If NBKPG > 0, then each user will potentially have NBKPG entries in TTBL to track backpage images for that user.
			</li>

	==Compiler variable table (VTBL)==		==Compiler variable table (VTBL)==

ELowell at 16:37, 29 April 2016

2016-04-29T16:37:47Z

← Older revision		Revision as of 16:37, 29 April 2016
Line 294:		Line 294:

	==See also==		==See also==
	{{Template: HLI topic list}}		{{Template: HLI programming topic list}}

	[[Category: Host Language Interface]]		[[Category: Host Language Interface]]