TurboIMAGE/XL Database Management System Reference Manual (30391-90012)

Table Of Contents
488 Chapter10
Internal Structures and Techniques
Large Size Datasets in TurboIMAGE/iX
database needs to be created in the entrynumber format, there is a new $CONTROL
LARGESET directive in DBSCHEMA. Once DBSCHEMA encounters this directive, it will
create the root file to support large datasets, and set the 'root version' to 'C6'. It may be
noted that a database, as a whole, will need to support large size datasets (in other words,
one can not define a particular dataset alone to be in entrynumber format).
DBUTIL
DBUTIL changes are nearly transparent to the user, except that show dbname all, will
have the following message, if entrynumber format is used:
This database supports dataset size > 80 GB
Also, if the migration process failed, a subsequent show dbname all will have the
following message:
Migration to large dataset failed. Please restore db from backup
All other commands in DBUTIL will behave as today.
DBINFO
DBINFO has been modified to return information on various features used by the
database. Now, DBINFO Mode 406, will return in the buffer element #17 the various
features used in the database. The word is interpreted as below:
Bit # Value/ Description
15
1: Database contains at least one expandable detail dataset
0: Database contains no expandable detail dataset
14
1: Database has at least one jumbo dataset
0: Database contains no jumbo sets
13
1: At least one master dataset in the database has a B-Tree
0: No datasets in the database have B-trees
12
1: Database has at least one expandable master dataset
0: Database contains no expandable master datasets
11
Unused
10
1: Database is in entrynumber format (i.e support for large size dataset available)
0: Database in entryname format (Dataset size can only be upto 80 GB)