Large request considerations - Revision history

JAL: add link

2018-05-22T19:08:56Z

add link

← Older revision		Revision as of 19:08, 22 May 2018
Line 152:		Line 152:
	===GTBL (global variable table)===		===GTBL (global variable table)===
	<p>		<p>
	Global variables, lists, found sets, images, screens, menus, and ~~REMEMBERed~~ positions in ~~FOR~~ loops are special mechanisms for communicating across ~~User Language~~ request boundaries, as described in [[Global features]]. </p>		Global variables, lists, found sets, images, screens, menus, and remembered positions in <var>For</var> loops are special mechanisms for communicating across SOUL request boundaries, as described in [[Global features]]. </p>
	<p>		<p>
	A GTBL entry is created when any global object is declared. In addition to the entries created by individual declarations, the last 32 bytes of your GTBL space allocation is reserved for a GTBL trailer. </p>		A GTBL entry is created when any global object is declared. In addition to the entries created by individual declarations, the last 32 bytes of your GTBL space allocation is reserved for a GTBL trailer. </p>
	<p>		<p>
	You can delete entries from GTBL by using different forms of the CLEAR statement, or the CLEARG or CLEARGO commands. See [[Global features#Clearing the GTBL work area\|Clearing the GTBL work area]] for detailed instructions on clearing objects. </p>		You can delete entries from GTBL by using different forms of the CLEAR statement, or the <var>CLEARG</var> or <var>CLEARGO</var> commands. See [[Global features#Clearing the GTBL work area\|Clearing the GTBL work area]] for detailed instructions on clearing objects. </p>
	<p>		<p>
	The types of GTBL entries are listed below:</p>		The types of GTBL entries are listed below:</p>
	<ul>		<ul>
	<li>A global variable (declared or changed with the $~~SETG~~ or $~~INCRG~~ function) creates an entry with a length of 4 bytes plus the length of the variable name plus the length of the current value. If a global variable is redefined, its old entry is deleted and a new entry is added. </li>		<li>A global variable (declared or changed with the <var>[[$Setg]]</var> or <var>[[$Incrg]]</var> function) creates an entry with a length of 4 bytes plus the length of the variable name plus the length of the current value. If a global variable is redefined, its old entry is deleted, and a new entry is added. </li>
	~~</li>~~
	<li>A global list or found set in single file context creates an entry with a length of 28 bytes.</li>		<li>A global list or found set in single file context creates an entry with a length of 28 bytes. </li>
	~~</li>~~
	<li>A global list or found set in group context creates an entry with a length of 28 bytes plus eight bytes for each file in the group.</li>		<li>A global list or found set in group context creates an entry with a length of 28 bytes plus eight bytes for each file in the group. </li>
	~~</li>~~
	<li>A sorted found set creates an entry with a length of 40 bytes.</li>		<li>A sorted found set creates an entry with a length of 40 bytes.</li>
	~~</li>~~
	<li>A position in an unordered or sorted record set creates an entry with a base length of 32 bytes.</li>		<li>A position in an unordered or sorted record set creates an entry with a base length of 32 bytes. </li>
	~~</li>~~
	<li>A position in a non-pattern driven ordered (BTREE) record set creates an entry with a length of 60 bytes plus a number of bytes equal to the size of the BTREE key.</li>		<li>A position in a non-pattern driven ordered (BTREE) record set creates an entry with a length of 60 bytes plus a number of bytes equal to the size of the BTREE key. </li>
	~~</li>~~
	<li>A position in a pattern driven ordered (BTREE) record set creates an entry with a length of 68 bytes.</li>		<li>A position in a pattern driven ordered (BTREE) record set creates an entry with a length of 68 bytes. </li>
	~~</li>~~
	<li>A position in a sorted file record set creates an entry with a length of 80 byes. ~~</li>~~		<li>A position in a sorted file record set creates an entry with a length of 80 byes. </li>
	</li>
	</ul>		</ul>
	<p>		<p>
Line 182:		Line 181:
	===ITBL (dummy string and $READ response table)===		===ITBL (dummy string and $READ response table)===
	<p>		<p>
	ITBL is used to hold dummy string and $~~READ~~ responses entered as arguments to an ~~INCLUDE~~ statement or command. </p>		ITBL is used to hold dummy string and <var>$Read</var> responses entered as arguments to an <var>Include</var> statement or command. </p>
	<p>		<p>
	Argument strings are saved as entered, including delimiters, with an additional 4 bytes of overhead for each saved string. </p>		Argument strings are saved as entered, including delimiters, with an additional 4 bytes of overhead for each saved string. </p>
	<p>		<p>
	Space taken by a string is released when the included procedure is exhausted. </p>		Space taken by a string is released when the included procedure is exhausted. </p>

	===NTBL (statement labels/list names/variables table)===		===NTBL (statement labels/list names/variables table)===
Line 679:		Line 678:
	====Value loops====		====Value loops====
	<ul>		<ul>
	<li>FOR EACH RECORD without the IN ORDER clause allocates a 16-byte entry.</li>		<li>FOR EACH RECORD without the IN ORDER clause allocates a 16-byte entry. </li>

	<li>FOR EACH VALUE with FROM, TO or LIKE specified, and/or using an ORDERED field allocates a 40-byte entry.</li>		<li>FOR EACH VALUE with FROM, TO or LIKE specified, and/or using an ORDERED field allocates a 40-byte entry. </li>

	<li>FOR EACH VALUE and FOR EACH RECORD IN ORDER BY, using an ORDERED field, allocate an additional 44-byte entry.</li>		<li>FOR EACH VALUE and FOR EACH RECORD IN ORDER BY, using an ORDERED field, allocate an additional 44-byte entry. </li>

	<li>Every ~~FOR~~ loop position declared with a ~~REMEMBER~~ statement adds an 8-byte entry.</li>		<li>Every <var>For</var> loop position declared with a <var>[[Remember statement\|Remember]]</var> statement adds an 8-byte entry. </li>

	<li>When an ON unit is invoked, one 28-byte entry is used. The entry is released by BYPASS, RETRY, or STOP.		<li>When an ON unit is invoked, one 28-byte entry is used. The entry is released by BYPASS, RETRY, or STOP. </li>
	</li>
	</ul>		</ul>
	<p>		<p>
	Many VTBL entries are deleted by the <var>[[#More command\|More]]</var> command. Entries are retained in the following cases:</p>		Many VTBL entries are deleted by the <var>[[#More command\|More]]</var> command. Entries are retained in the following cases: </p>
	<ul>		<ul>
	<li>%Variables</li>		<li>%Variables</li>

	<li>COUNT's 8-byte entry (Not retained if the original ~~User Language~~ statement was unlabeled.) </li>		<li>COUNT's 8-byte entry (Not retained if the original SOUL statement was unlabeled.) </li>

	<li>FIND's basic 8-byte (larger for groups) entry (Not retained if the original ~~User Language~~ statement was unlabeled.)</li>		<li>FIND's basic 8-byte (larger for groups) entry (Not retained if the original SOUL statement was unlabeled.)</li>

	<li>Entries for lists</li>		<li>Entries for lists</li>

JDamon: Updated description of TTBL with text from the "HLI: Model 204 tables" page

2016-05-11T21:53:33Z

Updated description of TTBL with text from the "HLI: Model 204 tables" page

← Older revision		Revision as of 21:53, 11 May 2016
Line 613:		Line 613:
	===TTBL (temporary work page list table)===		===TTBL (temporary work page list table)===
	<p>		<p>
	TTBL entries ~~keep track of scratch file (~~CCATEMP) pages. ~~The FIND statement uses scratch pages as a work space for evaluating Boolean expressions~~. ~~The~~ number of ~~TTBL entries depends~~ on the complexity of the ~~Boolean operation~~. TTBL ~~entries~~ are released at the ~~end of~~ the ~~evaluation of the FIND statement~~. </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>
			<ul>
			<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>
			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>

	===VTBL (compiler variable table)===		===VTBL (compiler variable table)===
	<p>		<p>

Dme at 11:58, 25 January 2015

2015-01-25T11:58:30Z

← Older revision		Revision as of 11:58, 25 January 2015
Line 143:		Line 143:
	<li>The first type is allocated each time a group is opened (explicitly by OPEN or implicitly for an ad hoc group) and is released when the group is closed. This type of entry has a fixed-size portion of 62 bytes, plus 2 bytes for each file in the group definition.</li>		<li>The first type is allocated each time a group is opened (explicitly by OPEN or implicitly for an ad hoc group) and is released when the group is closed. This type of entry has a fixed-size portion of 62 bytes, plus 2 bytes for each file in the group definition.</li>
	</li>		</li>
	<li>The second type is used for collecting field name codes and properties during a request. An entry is allocated each time a new field name is encountered in the request. The entry size is variable, consisting of 9 fixed bytes plus a number of bytes equal to the length of the field name plus 11 bytes for each file in the group. These field entries are deleted at the ~~END~~ statement (including ~~END MORE~~).</li>		<li>The second type is used for collecting field name codes and properties during a request. An entry is allocated each time a new field name is encountered in the request. The entry size is variable, consisting of 9 fixed bytes plus a number of bytes equal to the length of the field name plus 11 bytes for each file in the group. These field entries are deleted at the <var>End</var> statement (including <var>End More</var>).</li>
	</li>		</li>
	</ul>		</ul>
Line 192:		Line 192:
	One entry (12 bytes) is allocated in NTBL for each statement label, list name, %variable, and image, menu, and screen variable. An entry also is allocated for each partner process opened by a request. Data defined as common takes two entries for the first COMMON declaration and one additional entry for each additional COMMON declaration. </p>		One entry (12 bytes) is allocated in NTBL for each statement label, list name, %variable, and image, menu, and screen variable. An entry also is allocated for each partner process opened by a request. Data defined as common takes two entries for the first COMMON declaration and one additional entry for each additional COMMON declaration. </p>
	<p>		<p>
	One entry is allocated for each unlabeled FIND. An extra entry is allocated for each FOR EACH VALUE statement or each FOR statement with the IN ORDER clause. Most NTBL entries are preserved by ~~MORE~~, but the unlabeled FIND and secondary FOR entries are deleted. </p>		One entry is allocated for each unlabeled FIND. An extra entry is allocated for each FOR EACH VALUE statement or each FOR statement with the IN ORDER clause. Most NTBL entries are preserved by <var>More</var>, but the unlabeled FIND and secondary FOR entries are deleted. </p>
	<p>		<p>
	During request evaluation, one entry is required for each sequential or VSAM file opened simultaneously. </p>		During request evaluation, one entry is required for each sequential or VSAM file opened simultaneously. </p>
Line 567:		Line 567:
	</table>		</table>
	<p>		<p>
	QTBL is emptied by ~~END~~ and ~~END MORE~~ (see [[#Starting and ending requests and continuations\|Starting and ending requests and continuations]] for a discussion of ~~END MORE~~). </p>		QTBL is emptied by <var>End</var> and <var>End More</var> (see [[#Starting and ending requests and continuations\|Starting and ending requests and continuations]] for a discussion of <var>End More</var>). </p>

	===STBL (character string table)===		===STBL (character string table)===
Line 609:		Line 609:
	A FIXED or FLOAT %variable array uses 8 bytes of STBL space for each element. If the FIELD SAVE option is used when a STRING %variable array is declared (if field information is saved where the element is used for a field name variable), then 13 bytes plus the maximum length of the string plus 1 byte are reserved in STBL for each element of the array. If the NO FIELD SAVE option is specified, the extra 13 bytes for field information are not reserved. Using NO FIELD SAVE can result in a significant saving in a multi-dimension array. For example, in an array with dimensions 100 by 2, specifying NO FIELD SAVE saves 100213 (or 2600) bytes. </p>		A FIXED or FLOAT %variable array uses 8 bytes of STBL space for each element. If the FIELD SAVE option is used when a STRING %variable array is declared (if field information is saved where the element is used for a field name variable), then 13 bytes plus the maximum length of the string plus 1 byte are reserved in STBL for each element of the array. If the NO FIELD SAVE option is specified, the extra 13 bytes for field information are not reserved. Using NO FIELD SAVE can result in a significant saving in a multi-dimension array. For example, in an array with dimensions 100 by 2, specifying NO FIELD SAVE saves 100213 (or 2600) bytes. </p>
	<p>		<p>
	The ~~MORE command (see~~ [[#~~MORE~~ command\|~~MORE command~~]]) releases most STBL space, keeping only the entries used for %variables and arrays. STBL is filled in during evaluation, when a value is assigned to the %variable. The space in STBL is reused when the %variable is reassigned. </p>		The <var>[[#More command\|More]]</var> command releases most STBL space, keeping only the entries used for %variables and arrays. STBL is filled in during evaluation, when a value is assigned to the %variable. The space in STBL is reused when the %variable is reassigned. </p>

	===TTBL (temporary work page list table)===		===TTBL (temporary work page list table)===
Line 684:		Line 684:
	</ul>		</ul>
	<p>		<p>
	Many VTBL entries are deleted by the ~~MORE command (refer to~~ [[#~~MORE~~ command\|~~MORE command~~]]). Entries are retained in the following cases:</p>		Many VTBL entries are deleted by the <var>[[#More command\|More]]</var> command. Entries are retained in the following cases:</p>
	<ul>		<ul>
	<li>%Variables</li>		<li>%Variables</li>
Line 712:		Line 712:
	Specific benefits of request continuation include:</p>		Specific benefits of request continuation include:</p>
	<ul>		<ul>
	<li>The opportunity to enter certain <var class="product">Model 204</var> commands between a request terminated by ~~END MORE~~ and its continuation.</li>		<li>The opportunity to enter certain <var class="product">Model 204</var> commands between a request terminated by <var>End More</var> and its continuation.</li>
	<li>The ability to decide whether to continue a request based on its (intermediate) results.</li>		<li>The ability to decide whether to continue a request based on its (intermediate) results.</li>
	<li>The opportunity to reduce the size of your QTBL, since this work area is cleared with the execution of an ~~END MORE~~ statement (unlike other work areas, which retain their contents when ~~END MORE~~ is encountered).</li>		<li>The opportunity to reduce the size of your QTBL, since this work area is cleared with the execution of an <var>End More</var> statement (unlike other work areas, which retain their contents when <var>End More</var> is encountered).</li>
	</ul>		</ul>
	<p>		<p>
	See the next section for rules relating to the use of request continuation.</p>		See the next section for rules relating to the use of request continuation.</p>

	===~~MORE~~ command===		===More command===

	====Description====		====Description====
Line 781:		Line 781:
	===Starting and ending requests and continuations===		===Starting and ending requests and continuations===
	<p>		<p>
	A request is started by a ~~BEGIN~~ command; a continuation is started by a ~~MORE~~ command. Both are terminated by ~~END~~ or ~~END MORE~~ statements (with a USE specification if desired).</p>		A request is started by a <var>Begin</var> command; a continuation is started by a <var>More</var> command. Both are terminated by <var>End</var> or <var>End More</var> statements (with a USE specification if desired).</p>

	===Multiple continuations===		===Multiple continuations===
	<p>		<p>
	You can continue a request several times, as long as you issue an ~~END MORE~~ statement at the end of each section to be continued. Each new continuation, the initial request, and all previous continuations constitute the basic request. Once a request or a continuation ends with an END statement without the ~~MORE~~ option, it is no longer continued.</p>		You can continue a request several times, as long as you issue an <var>End More</var> statement at the end of each section to be continued. Each new continuation, the initial request, and all previous continuations constitute the basic request. Once a request or a continuation ends with an END statement without the <var>More</var> option, it is no longer continued.</p>

	===References in a continuation===		===References in a continuation===
Line 805:		Line 805:
	Statement labels for statements other than COUNT, FIND, and SORT in the basic request can be reused in the continuation.</p>		Statement labels for statements other than COUNT, FIND, and SORT in the basic request can be reused in the continuation.</p>
	<p>		<p>
	When a request is continued, all found sets, lists, and %variables of the main request are preserved for later use. The found sets, lists, and %variables of complex subroutines are discarded after ~~END MORE~~ unless they are common. </p>		When a request is continued, all found sets, lists, and %variables of the main request are preserved for later use. The found sets, lists, and %variables of complex subroutines are discarded after <var>End More</var> unless they are common. </p>
	<p>		<p>
	If a request opens a data set, and you want to leave the data set open after the request terminates, you can end the request with ~~END MORE USE~~. This allows the continuation to add to the USE output without resetting the page number.</p>		If a request opens a data set, and you want to leave the data set open after the request terminates, you can end the request with <var>End More Use</var>. This allows the continuation to add to the USE output without resetting the page number.</p>

	===Restrictions applying to request continuations===		===Restrictions applying to request continuations===
Line 845:		Line 845:
	===ON units===		===ON units===
	<p>		<p>
	An ON unit definition is not preserved across an ~~END MORE~~ statement and ~~MORE~~ command. Each new request continuation must define its own ON units. </p>		An ON unit definition is not preserved across an <var>End More</var> statement and <var>More</var> command. Each new request continuation must define its own ON units. </p>

	===Interaction with SORT statement===		===Interaction with SORT statement===

Dme: /* Description */

2015-01-25T10:45:36Z

Description

← Older revision		Revision as of 10:45, 25 January 2015
Line 723:		Line 723:
	====Description====		====Description====
	<p>		<p>
	If a ~~BEGIN~~ command is replaced by the ~~MORE~~ command, the request that follows is considered to be a continuation of the previous request and can refer to statement labels and other information from that request. </p>		If a <var>Begin</var> command is replaced by the <var>More</var> command, the request that follows is considered to be a continuation of the previous request and can refer to statement labels and other information from that request. </p>

	====Example 1====		====Example 1====
	<p>		<p>

JAL: remove Sys Man guide

2014-10-31T22:31:28Z

remove Sys Man guide

← Older revision		Revision as of 22:31, 31 October 2014
Line 200:		Line 200:
	Each statement is compiled into internal <var class="product">Model 204</var> instructions in QTBL. After compilation, the entries in QTBL are used to drive the evaluator. The entries generated by each User Language statement vary in number and in size. </p>		Each statement is compiled into internal <var class="product">Model 204</var> instructions in QTBL. After compilation, the entries in QTBL are used to drive the evaluator. The entries generated by each User Language statement vary in number and in size. </p>
	<p>		<p>
	Under certain circumstances, users sharing precompiled procedures can use a shared version of QTBL, thus reducing server I/O. See ~~the <var class="book">~~[~~http://www.rocketsoftware.com/m204/products/model204/documentation/v7r4/M204-System-Mgr/view Rocket Model 204 System Manager's Guide~~]~~</var>~~ for more information.</p>		Under certain circumstances, users sharing precompiled procedures can use a shared version of QTBL, thus reducing server I/O. See [[Performance monitoring and tuning#Resident Request feature for precompiled procedures\|Resident Request feature for precompiled procedures]] for more information.</p>
	<p>		<p>
	Some common examples are listed below: </p>		Some common examples are listed below: </p>

JAL at 20:23, 3 February 2014

2014-02-03T20:23:37Z

← Older revision		Revision as of 20:23, 3 February 2014
Line 1:		Line 1:
			<div class="toclimit-3">

	==Overview==		==Overview==
	<p>		<p>
Line 855:		Line 857:
	a continuation retrieves only the AGENT field from the sorted records. All other fields are treated as missing in the sorted records. </p>		a continuation retrieves only the AGENT field from the sorted records. All other fields are treated as missing in the sorted records. </p>

			</div> <!-- end of toc limit div -->

	[[Category:SOUL]]		[[Category:SOUL]]

JAL: /* VTBL (the compiler variable table) */

2014-02-03T20:22:00Z

VTBL (the compiler variable table)

← Older revision		Revision as of 20:22, 3 February 2014
Line 613:		Line 613:
	TTBL entries keep track of scratch file (CCATEMP) pages. The FIND statement uses scratch pages as a work space for evaluating Boolean expressions. The number of TTBL entries depends on the complexity of the Boolean operation. TTBL entries are released at the end of the evaluation of the FIND statement. </p>		TTBL entries keep track of scratch file (CCATEMP) pages. The FIND statement uses scratch pages as a work space for evaluating Boolean expressions. The number of TTBL entries depends on the complexity of the Boolean operation. TTBL entries are released at the end of the evaluation of the FIND statement. </p>

	===VTBL (~~the~~ compiler variable table)===		===VTBL (compiler variable table)===
	<p>		<p>
	Entries in VTBL vary in size. Most range from 8 to 20 bytes; some are much larger. Many User Language statements and some constructs cause one or more compiler variables to be allocated in VTBL. Common examples are listed in the following sections. </p>		Entries in VTBL vary in size. Most range from 8 to 20 bytes; some are much larger. Many User Language statements and some constructs cause one or more compiler variables to be allocated in VTBL. Common examples are listed in the following sections. </p>

JAL: /* VTBL, the compiler variable table */

2014-02-03T20:21:34Z

VTBL, the compiler variable table

← Older revision		Revision as of 20:21, 3 February 2014
Line 613:		Line 613:
	TTBL entries keep track of scratch file (CCATEMP) pages. The FIND statement uses scratch pages as a work space for evaluating Boolean expressions. The number of TTBL entries depends on the complexity of the Boolean operation. TTBL entries are released at the end of the evaluation of the FIND statement. </p>		TTBL entries keep track of scratch file (CCATEMP) pages. The FIND statement uses scratch pages as a work space for evaluating Boolean expressions. The number of TTBL entries depends on the complexity of the Boolean operation. TTBL entries are released at the end of the evaluation of the FIND statement. </p>

	===VTBL, the compiler variable table===		===VTBL (the compiler variable table)===
	<p>		<p>
	Entries in VTBL vary in size. Most range from 8 to 20 bytes; some are much larger. Many User Language statements and some constructs cause one or more compiler variables to be allocated in VTBL. Common examples are listed in the following sections. </p>		Entries in VTBL vary in size. Most range from 8 to 20 bytes; some are much larger. Many User Language statements and some constructs cause one or more compiler variables to be allocated in VTBL. Common examples are listed in the following sections. </p>
Line 699:		Line 699:
	<p>		<p>
	Entries in the last three categories are not retained if the original User Language statement was not labeled. </p>		Entries in the last three categories are not retained if the original User Language statement was not labeled. </p>

	==Request continuation==		==Request continuation==
	<p>		<p>

JAL: more conversion cleanup

2014-01-14T22:36:56Z

more conversion cleanup

Show changes

JAL at 19:47, 2 January 2014

2014-01-02T19:47:50Z

← Older revision		Revision as of 19:47, 2 January 2014
Line 105:		Line 105:
	</ul>		</ul>
	<p>In addition to the space required by the two types of entries described above, <var class="product">Model 204</var> allocates a fixed amount of space in FTBL equal to 4 bytes times the value of the NGROUP runtime parameter. </p>		<p>In addition to the space required by the two types of entries described above, <var class="product">Model 204</var> allocates a fixed amount of space in FTBL equal to 4 bytes times the value of the NGROUP runtime parameter. </p>

	====GTBL (global variable table)====		====GTBL (global variable table)====
	<p>Global variables, lists, found sets, images, screens, menus, and REMEMBERed positions in FOR loops are special mechanisms for communicating across User Language request boundaries, as described in [[Global ~~Features#Global Features\|Global Features~~]]. </p>		<p>Global variables, lists, found sets, images, screens, menus, and REMEMBERed positions in FOR loops are special mechanisms for communicating across User Language request boundaries, as described in [[Global features]]. </p>
	<p>A GTBL entry is created when any global object is declared. In addition to the entries created by individual declarations, the last 32 bytes of your GTBL space allocation is reserved for a GTBL trailer. </p>		<p>A GTBL entry is created when any global object is declared. In addition to the entries created by individual declarations, the last 32 bytes of your GTBL space allocation is reserved for a GTBL trailer. </p>
	<p>You can delete entries from GTBL by using different forms of the CLEAR statement, or the CLEARG or CLEARGO commands. See [[Global ~~Features~~#Clearing the GTBL work area\|Clearing the GTBL work area]] for detailed instructions on clearing objects. </p>		<p>You can delete entries from GTBL by using different forms of the CLEAR statement, or the CLEARG or CLEARGO commands. See [[Global features#Clearing the GTBL work area\|Clearing the GTBL work area]] for detailed instructions on clearing objects. </p>
	<p>The types of GTBL entries are listed below:</p>		<p>The types of GTBL entries are listed below:</p>
	<ul>		<ul>