In Version 15.0, there is support for both dynamic extend of the Temporary Table Manager (TTM) work table used by SQL and for an on-demand dynamic extend of the TTM table at your request. These dynamic extends can be done with no loss of access to any other task areas or TTM usage. You need not close the TTM nor therefore reopen it later. Support is provided when the TTM is defined as either DASD or VIRTUAL. When the TTM is DASD, the normal dynamic extend ability is supported for the TTM. When the TTM is VIRTUAL, the dynamic extend or on-demand dynamic extend is supported. Dynamic extend and on-demand dynamic extend are fully supported to your specifications.
Specifying dynamic extend at MUF startup is done using MUF startup options as described in the Database and System Administration Guide.
Changing dynamic extend settings after the MUF has started is done using the VIRTUAL_DYNAMIC_EXTEND console-like command as described in the Database and System Administration Guide.
An on-demand dynamic extend is done using the DYNAMIC_EXTEND console-like command described in the Database and System Administration Guide.
The TTM can be found to be too small when using the ALTER TABLE statement (see ALTER TABLE).
A new column, TTM_BLKS_MAX_USE, that lists the highest number of 4K-blocks used, has been added to the SQL_STATUS table (see SQL_STATUS (SQS)).
If a TTM becomes full or is too small, you can receive SQL codes -560 (see -560 - TEMPORARY TABLE AREA (TTM) FULL)and -561 (see -561 - TTM TOO SMALL, SEE ERROR ACTION).
|
Copyright © 2014 CA.
All rights reserved.
|
|