UTABLE command

From m204wiki
Revision as of 23:42, 2 December 2014 by JAL (talk | contribs) (→‎Syntax)
Jump to navigation Jump to search

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 is not reset.
parameter A Model 204 user table (UTABLE) parameter.
value The new value of the parameter.

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 120%

Example

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 reset the following parameters using the UTABLE command:

Number of bytes in the user pushdown list
ParameterMeaning
HTLENMaximum length of a User Language 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
LPDLST
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

You can specify any number of user table parameters. For information on specifying parameter values, refer to Chapter 1.

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.

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.

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.