GTBLPCT parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
| Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V5.1</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The GTBLPCT parameter indicates the initial percentage of GTBL to allocate for storage of global string variables; the remaining storage area is for global objects such as global screens, images, lists, found sets, and positions.</p> | <p>The GTBLPCT parameter indicates the initial percentage of GTBL to allocate for storage of global string variables; the remaining storage area is for global objects such as global screens, images, lists, found sets, and positions.</p> | ||
Revision as of 12:36, 28 October 2014
Initial GTBL percentage to allocate for plain globals
Summary
- Default value
- 50
- Parameter type
- User
- Where set
- By any user
- Related products
- All
- Introduced
- Model 204 V5.1
Description
The GTBLPCT parameter indicates the initial percentage of GTBL to allocate for storage of global string variables; the remaining storage area is for global objects such as global screens, images, lists, found sets, and positions.
The GTBLPCT parameter has no effect if GTBLHASH=0.
Resetting the GTBLPCT parameter clears the global table.
Rocket Software recommends that you set GTBLPCT high, if you have mostly global strings and a few global objects; low, if the reverse applies. For a discussion of the performance improvement in handling global variables see the Rocket Model 204 User Language Manual.