UTABLE command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
 
(12 intermediate revisions by 3 users not shown)
Line 6: Line 6:
<dd>Sets or calculates the size of your server tables
<dd>Sets or calculates the size of your server tables
</dl>
</dl>
==Syntax==
==Syntax==
<p class="syntax">UTABLE [(SIZE)] parameter=value
<p class="syntax">UTABLE [(SIZE)] <span class="term">parameter</span>=<span class="term">value</span> [,<span class="term">parameter</span>=<span class="term">value</span>] ...
[,parameter=value] ...
</p>
</p>
   
   
<b>Where:</b>
Where:
<table>  
<table>  
<tr>
<tr>
<th><var>SIZE</var></th>
<th><var>SIZE</var></th>
<td> indicates that the overall size of the server is calculated, but that the table sizes is not reset.</td>
<td>Indicates that the overall size of the server is calculated, but that the table sizes are not reset.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>parameter</th>
<th>parameter</th>
<td> is a <var class="product">Model&nbsp;204</var> user table (UTABLE) parameter.</td>
<td>A <var class="product">Model&nbsp;204</var> user table (<var>UTABLE</var>) parameter. These parameters are listed below in the [[#Usage notes|Usage notes]] section.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>value</th>
<th>value</th>
<td> is the new value of the parameter.</td>
<td>The new value of the parameter.
<p>To indicate a new value [[Relative values for Model 204 numeric parameters|relative]] to the current value of the parameter, use a following plus sign (+), minus sign (-), or percent sign (%) as the relative value indicator. No space is allowed between the numeric value and the relative value indicator. See the [[#Examples|examples]] below.</p></td>
</tr>
</tr>
</table>
</table>
===Syntax notes===
===Syntax notes===
Equal signs and commas are optional.
<p>
==Example==
Equal signs are optional.</p>
<p class="code">UTABLE LNTBL = 100 LSTBL = 700
Commas between parameters are optional unless the relative (<tt>+</tt>, <tt>-</tt>, <tt>%</tt>) or shortcut (<var>K</var>, <var>M</var>, <var>G</var>, or <var>E</var>) parameters are used. These parameters require EOL, blank, or a comma as a delimiter.
 
==Examples==
<p class="code">UTABLE LFTBL 1K, LGTBL 1K</p>
<p class="code">UTABLE LSTBL 10000+</p>
<p class="code">UTABLE LSTBL 10000-</p>
<p class="code">UTABLE LSTBL 120%</p>
<p class="code"><b>UTABLE LNTBL = 100 LSTBL = 700</b>
LNTBL 100    LENGTH OF NTBL
LNTBL 100    LENGTH OF NTBL
LSTBL 700    LENGTH OF STBL
LSTBL 700    LENGTH OF STBL
<b></b>*** M204.0098: MINIMUM SERVSIZE FOR THESE TABLES = 47448
<b></b>*** M204.0098: MINIMUM SERVSIZE FOR THESE TABLES = 47448
</p>
</p>
==Usage notes==
==Usage notes==
<p>The UTABLE command allows a user to change the size of the server tables or to help determine the minimum SERVSIZE value needed for tables of specified sizes.</p>
<ul>
<p>You can reset the following parameters using the UTABLE command:</p>
<li>The <var>UTABLE</var> command allows a user to change the size of the server tables or to help determine the minimum <var>[[SERVSIZE parameter|SERVSIZE]]</var> value needed for tables of specified sizes. You can view the value of any parameter with the <var>[[VIEW command|VIEW</var>]] command.</li>
 
<li>You can reset the following parameters using the <var>UTABLE</var> command. You can specify any number of them. For information on specifying parameter values, refer to [[Overview of Model 204 parameters]].
<table>
<table>
<tr><th>Parameter</th><th>Meaning</th></tr>
<tr class="head"><th>Parameter</th><th>Meaning</th></tr>
<tr><td><var>HTLEN</var></td><td>Maximum length of a User Language header or trailer</td></tr>
<tr><td><var>HTLEN</var></td><td>Maximum length of a SOUL header or trailer</td></tr>
<tr><td><var>LFSCB</var></td><td>Number of bytes in the full screen buffer<td></tr>
 
<tr><td><var>LFSCB</var></td><td>Number of bytes in the full screen buffer</td></tr>
 
<tr><td><var>LFTBL</var></td><td>Number of bytes in FTBL</td></tr>
<tr><td><var>LFTBL</var></td><td>Number of bytes in FTBL</td></tr>
<tr><td><var>LGTBL</var></td><td>Number of bytes in GTBL</td></tr>
<tr><td><var>LGTBL</var></td><td>Number of bytes in GTBL</td></tr>
<tr><td><var>LHEAP</var></td><td>Number of bytes in the HEAP storage area</td></tr>
<tr><td><var>LHEAP</var></td><td>Number of bytes in the HEAP storage area</td></tr>
<tr><td><var>LITBL</var></td><td>Number of bytes in ITBL</td></tr>
<tr><td><var>LITBL</var></td><td>Number of bytes in ITBL</td></tr>
<tr><td><var>LNTBL</var></td><td>Number of 12 byte entries in NTBL</td></tr>
 
<tr><td><var>LPDLST</var></td>Number of bytes in the user pushdown list<td></td></tr>
<tr><td><var>LNTBL</var></td><td>Number of 12-byte entries in NTBL</td></tr>
<tr><td><var>LQTBL</var></td><td>Number of 16 byte entries in QTBL</td></tr>
 
<tr><td><var>LPDLST</var></td><td>Number of bytes in the user pushdown list</td></tr>
 
<tr><td><var>LQTBL</var></td><td>Number of 16-byte entries in QTBL</td></tr>
 
<tr><td><var>LSTBL</var></td><td>Number of bytes in STBL</td></tr>
<tr><td><var>LSTBL</var></td><td>Number of bytes in STBL</td></tr>
<tr><td><var>LTTBL</var></td><td>Number of 4 byte entries in the temporary work page list table, TTBL</td></tr>
 
<tr><td><var>LVTBL</var></td><td>Number of 32 byte entries in the table of compiler variables, VTBL</td></tr>
<tr><td><var>LTTBL</var></td><td>Number of 4-byte entries in the temporary work page list table, TTBL</td></tr>
 
<tr><td><var>LVTBL</var></td><td>Number of 32-byte entries in the table of compiler variables, VTBL</td></tr>
 
<tr><td><var>LXTBL</var></td><td>Number of bytes in XTBL</td></tr>
<tr><td><var>LXTBL</var></td><td>Number of bytes in XTBL</td></tr>
<tr><td><var>MAXHDR</var></td><td>Maximum number of output page header lines, each of length up to <var>HTLEN</var> that can be defined within a single SOUL request</td></tr>
<tr><td><var>MAXHDR</var></td><td>Maximum number of output page header lines, each of length up to <var>HTLEN</var> that can be defined within a single SOUL request</td></tr>
<tr><td><var>MAXTRL</var></td><td>Maximum number of output page trailer lines, each of length up to <var>HTLEN</var> that can be defined within a single SOUL request</td></tr>
<tr><td><var>MAXTRL</var></td><td>Maximum number of output page trailer lines, each of length up to <var>HTLEN</var> that can be defined within a single SOUL request</td></tr>
</table>
</table></li>
<p>You can specify any number of user table parameters. For information on specifying parameter values, refer to Chapter 1. </p>
 
<p>If a User Language application makes extensive use of file groups, you can optimize server utilization by adjusting table sizes while files or groups are open.</p>
<li>If a SOUL application makes extensive use of file groups, you can optimize server utilization by adjusting table sizes while files or groups are open.
<p>When changing table sizes for open files or groups, keep the following restrictions and interdependencies in mind: </p>
<p>
When changing table sizes for open files or groups, keep the following restrictions and interdependencies in mind: </p>
<ul>
<ul>
<li>
<li>
<p>If you request an LFTBL size that is smaller than the amount required by your currently open groups, the following message is displayed: </p>
<p>
If you request an <var>LFTBL</var> size that is smaller than the amount required by your currently open groups, the following message is displayed: </p>
<p class="code">*** M204.1941: NEW LFTBL MUST BE AT LEAST nn, FILES MUST BE CLOSED
<p class="code">*** M204.1941: NEW LFTBL MUST BE AT LEAST nn, FILES MUST BE CLOSED
</p>
</p>
Line 69: Line 96:
   
   
<li>
<li>
<p>If you change either LFTBL or LXTBL, and you have entries in your XTBL, the following message is displayed:</p>
<p>If you change either <var>LFTBL</var> or <var>LXTBL</var>, and you have entries in your XTBL, the following message is displayed:</p>
<p class="code">*** M204.0100: FILES MUST BE CLOSED TO CHANGE XTBL
<p class="code">*** M204.0100: FILES MUST BE CLOSED TO CHANGE XTBL
</p>
</p>
Line 75: Line 102:
   
   
<li>
<li>
<p>If you change LFTBL, LXTBL, or LGTBL, and you have entries in your GTBL, then the following message is displayed: </p>
<p>If you change <var>LFTBL</var>, <var>LXTBL</var>, or <var>LGTBL</var>, and you have entries in your GTBL, then the following message is displayed: </p>
<p class="code">*** M204.0101: ALLOCATED GLOBALS WILL BE CLEARED
<p class="code">*** M204.0101: ALLOCATED GLOBALS WILL BE CLEARED
</p>
</p>
Line 81: Line 108:
   
   
<li>
<li>
<p>If you change LFTBL, LXTBL, LGTBL, or LITBL, and you have stacked $READ arguments in your ITBL, then the following message is displayed: </p>
<p>If you change <var>LFTBL</var>, <var>LXTBL</var>, <var>LGTBL</var>, or <var>LITBL</var>, and you have stacked <var>$Read</var> arguments in your ITBL, then the following message is displayed: </p>
<p class="code">*** M204.0102: LITBL RESET CLEARS STACKED ARGUMENTS
<p class="code">*** M204.0102: LITBL RESET CLEARS STACKED ARGUMENTS
</p>
</p>
Line 87: Line 114:
   
   
<li>
<li>
<p>If you are in an application subsystem and either of the "FILES MUST BE CLOSED" messages is issued (M204.1941 or M204.0100), then the following message is issued and the UTABLE command is terminated: </p>
<p>If you are in an application subsystem and either of the "FILES MUST BE CLOSED" messages is issued (M204.1941 or M204.0100), then the following message is issued and the <var>UTABLE</var> command is terminated: </p>
<p class="code">*** M204.1195: CAN'T CLOSE ALL FILES FROM A SUBSYSTEM
<p class="code">*** M204.1195: CAN'T CLOSE ALL FILES FROM A SUBSYSTEM
</p>
</p>
Line 93: Line 120:
   
   
<li>
<li>
<p>If you are not in an application subsystem and any of the conditions described above occurs, the following message is displayed and you can elect to terminate the operation by entering N: </p>
<p>If you are not in an application subsystem and any of the conditions described above occurs, the following message is displayed and you can elect to terminate the operation by entering <code>N</code>: </p>
<p class="code">*** M204.1076: DO YOU REALLY WANT TO CONTINUE?
<p class="code">*** M204.1076: DO YOU REALLY WANT TO CONTINUE?
</p>
</p>
<p>If you enter Y, all open files and groups are closed. If M204.1195 or M204.0100 were issued, GTBL and/or ITBL are cleared, and the UTABLE command continues processing. </p>
<p>
If you enter <code>Y</code>, all open files and groups are closed. If M204.1195 or M204.0100 were issued, GTBL and/or ITBL are cleared, and the <var>UTABLE</var> command continues processing. </p>
</li>
</li>
</ul>
</ul></li>
<p>Changing the size of any table using UTABLE causes an outstanding END MORE to be canceled.</p>
 
<p>An increase in size of one server table can require a decrease in size of one or more of the other server tables. This happens if you are already in the largest server and all available table space within the server has been used.     </p>
<li>Setting a relative value is supported as of version 7.5 of Model 204 or version 8.0 of the Sirius Mods.</li>
[[Category: General user commands]]
 
<li>Changing the size of any table using <var>UTABLE</var> causes an outstanding <var>END MORE</var> to be canceled.</li>
 
<li>An increase in size of one server table can require a decrease in size of one or more of the other server tables. This happens if you are already in the largest server and all available table space within the server has been used. </li>
</ul>
 
==See also==
<p>For details on resetting any Model 204 parameter, see the <var>[[RESET command|RESET]]</var> command.</p>  
For a complete listing of Model 204 parameters, see [[List of Model 204 parameters]].
 
[[Category: User commands]]
[[Category:Commands]]
[[Category:Commands]]

Latest revision as of 16:31, 22 March 2017

Summary

Privileges
Any user
Function
Sets or calculates the size of your server tables

Syntax

UTABLE [(SIZE)] parameter=value [,parameter=value] ...

Where:

SIZE Indicates that the overall size of the server is calculated, but that the table sizes are not reset.
parameter A Model 204 user table (UTABLE) parameter. These parameters are listed below in the Usage notes section.
value The new value of the parameter.

To indicate a new value relative to the current value of the parameter, use a following plus sign (+), minus sign (-), or percent sign (%) as the relative value indicator. No space is allowed between the numeric value and the relative value indicator. See the examples below.

Syntax notes

Equal signs are optional.

Commas between parameters are optional unless the relative (+, -, %) or shortcut (K, M, G, or E) parameters are used. These parameters require EOL, blank, or a comma as a delimiter.

Examples

UTABLE LFTBL 1K, LGTBL 1K

UTABLE LSTBL 10000+

UTABLE LSTBL 10000-

UTABLE LSTBL 120%

UTABLE LNTBL = 100 LSTBL = 700 LNTBL 100 LENGTH OF NTBL LSTBL 700 LENGTH OF STBL *** M204.0098: MINIMUM SERVSIZE FOR THESE TABLES = 47448

Usage notes

  • The UTABLE command allows a user to change the size of the server tables or to help determine the minimum SERVSIZE value needed for tables of specified sizes. You can view the value of any parameter with the VIEW command.
  • You can reset the following parameters using the UTABLE command. You can specify any number of them. For information on specifying parameter values, refer to Overview of Model 204 parameters.
    ParameterMeaning
    HTLENMaximum length of a SOUL header or trailer
    LFSCBNumber of bytes in the full screen buffer
    LFTBLNumber of bytes in FTBL
    LGTBLNumber of bytes in GTBL
    LHEAPNumber of bytes in the HEAP storage area
    LITBLNumber of bytes in ITBL
    LNTBLNumber of 12-byte entries in NTBL
    LPDLSTNumber of bytes in the user pushdown list
    LQTBLNumber of 16-byte entries in QTBL
    LSTBLNumber of bytes in STBL
    LTTBLNumber of 4-byte entries in the temporary work page list table, TTBL
    LVTBLNumber of 32-byte entries in the table of compiler variables, VTBL
    LXTBLNumber of bytes in XTBL
    MAXHDRMaximum number of output page header lines, each of length up to HTLEN that can be defined within a single SOUL request
    MAXTRLMaximum number of output page trailer lines, each of length up to HTLEN that can be defined within a single SOUL request
  • If a SOUL application makes extensive use of file groups, you can optimize server utilization by adjusting table sizes while files or groups are open.

    When changing table sizes for open files or groups, keep the following restrictions and interdependencies in mind:

    • If you request an LFTBL size that is smaller than the amount required by your currently open groups, the following message is displayed:

      *** M204.1941: NEW LFTBL MUST BE AT LEAST nn, FILES MUST BE CLOSED

    • If you change either LFTBL or LXTBL, and you have entries in your XTBL, the following message is displayed:

      *** M204.0100: FILES MUST BE CLOSED TO CHANGE XTBL

    • If you change LFTBL, LXTBL, or LGTBL, and you have entries in your GTBL, then the following message is displayed:

      *** M204.0101: ALLOCATED GLOBALS WILL BE CLEARED

    • If you change LFTBL, LXTBL, LGTBL, or LITBL, and you have stacked $Read arguments in your ITBL, then the following message is displayed:

      *** M204.0102: LITBL RESET CLEARS STACKED ARGUMENTS

    • If you are in an application subsystem and either of the "FILES MUST BE CLOSED" messages is issued (M204.1941 or M204.0100), then the following message is issued and the UTABLE command is terminated:

      *** M204.1195: CAN'T CLOSE ALL FILES FROM A SUBSYSTEM

    • If you are not in an application subsystem and any of the conditions described above occurs, the following message is displayed and you can elect to terminate the operation by entering N:

      *** M204.1076: DO YOU REALLY WANT TO CONTINUE?

      If you enter Y, all open files and groups are closed. If M204.1195 or M204.0100 were issued, GTBL and/or ITBL are cleared, and the UTABLE command continues processing.

  • Setting a relative value is supported as of version 7.5 of Model 204 or version 8.0 of the Sirius Mods.
  • Changing the size of any table using UTABLE causes an outstanding END MORE to be canceled.
  • An increase in size of one server table can require a decrease in size of one or more of the other server tables. This happens if you are already in the largest server and all available table space within the server has been used.

See also

For details on resetting any Model 204 parameter, see the RESET command.

For a complete listing of Model 204 parameters, see List of Model 204 parameters.