Communicator e3000 MPE/iX Release 6.5 Express 2 (Software Release C.65.02) (30216-90322)

60 Chapter4

Increases in Limits

Large Size Datasets in TurboIMAGE/iX

slot within the block of 5.

Now we can use a full 32-bit number to refer a record number. We call this 'entrynumber'

format. So, the 101st record in a dataset will be represented as just 101, irrespective of the

blocking factor used.

All existing databases prior to this release use entryname format. With this solution, a

database can be created either in the entrynumber format or the entryname format.

However, if large datasets greater than 80 GB are to be created, it can be done only if the

database is created in entrynumber format.

Changes in User Interfaces

DBSCHEMA

To protect existing database environments and scripts, the new DBSCHEMA (version

C.09.00 of IMAGE) will create databases in entryname format by default. However, if a

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 ﬁle 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 deﬁne 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 modiﬁed 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

1: Database contains at least one expandable detail dataset

0: Database contains no expandable detail dataset

1: Database has at least one jumbo dataset

0: Database contains no jumbo sets