TurboIMAGE/XL Database Management System Reference Manual (30391-90012)
Table Of Contents
- 1 Introduction
- 2 Database Structure and Protection
- 3 Defining a Database
- 4 Using the Database
- 5 TurboIMAGE/XL Library Procedures
- Using TurboIMAGE/XL Intrinsics
- DBBEGIN
- DBCLOSE
- DBCONTROL
- DBDELETE
- DBEND
- DBERROR
- DBEXPLAIN
- DBFIND
- DBGET
- DBINFO
- INTRINSIC NUMBER 402
- Syntax
- Parameters
- Discussion
- Mode 101: Item Number
- Mode 102: Item Name
- Mode 103: Items in Database
- Mode 104: Items in Data Set
- Mode 113: BTREEMODE1 and Wildcard Character
- Mode 201: Set Number
- Mode 202: Set Name
- Mode 203: Sets in Database
- Mode 204: Sets with Item
- Mode 205: Set Capacity
- Mode 206: Number of Data Set Chunks
- Mode 207: Size of Data Set Chunks
- Mode 208: Primary and Actual Capacity
- Mode 209: B-Tree Attachment
- Mode 301: Paths
- Mode 302: Key or Search Item
- Mode 401: Logging
- Mode 402: ILR
- Mode 403: Dynamic Roll-Back
- Mode 404: Logging Subsystem Information
- Mode 406: Database Information
- Mode 501: Subsystem Access
- Mode 502: Critical Item Update
- Modes 8nn: Third-Party Indexing
- Mode 901: Language
- DBLOCK
- DBMEMO
- DBOPEN
- DBPUT
- DBUNLOCK
- DBUPDATE
- DBXBEGIN
- DBXEND
- DBXUNDO
- 6 Host Language Access
- Model Program
- ORDERS Database Model Program
- Main Body of Program
- Opening the Database
- Retrieving All the Records on a Chain (with Item Level Locking)
- Retrieving a Data Entry Using a Record Number
- Retrieving Master Data Using a Key Value
- Retrieving Data Serially (with Set Level Locking)
- Adding an Entry
- Updating an Entry
- Deleting an Entry
- Rewinding a Data Set
- Obtaining Database Information
- Obtaining Error Messages and Explanations
- Closing the Database
- C
- COBOL II
- Defining Data Types, Variables, and Intrinsics
- Main Body of Program
- Opening the Database
- Retrieving All the Records on a Chain (with Item Level Locking)
- Retrieving a Data Entry Using a Record Number
- Retrieving Master Data Using a Key Value
- Retrieving Data Serially (with Set Level Locking)
- Adding an Entry
- Updating an Entry
- Deleting an Entry
- Rewinding a Data Set
- Obtaining Database Information
- Obtaining Error Messages and Explanations
- Closing the Database
- FORTRAN 77
- Pascal
- RPG
- 7 Logging and Recovery
- Database Utilities Used in Logging and Recovery
- Recovery Options
- Logical Transactions
- Dynamic Roll-Back Recovery
- Intrinsic Level Recovery
- Logging Preparation
- Step 1--Checking MPE/iX Logging Configuration
- Step 2--Acquiring Logging Capability
- Step 3--Logging to Tape or Disk
- Step 4--Building a Log File for Logging to Disk
- Step 5--Creating the Log Identifier
- Step 6--Setting the Log Identifier
- Step 7--Setting Flags for the Database Backup Copy
- Step 8--Making a Database Backup Copy
- TurboSTORE/iX 7x24 True-Online Backup
- Logging Status
- Logging Maintenance
- Roll-Forward Recovery
- Roll-Back Recovery
- DBRECOV Commands Used with Roll-Forward and Roll-Back Recovery
- Recovery Tables
- Post-Recovery Options
- The Mirror Database
- 8 Using the Database Utilities
- Restructuring the Database with TurboIMAGE/XL Utilities
- Summary of Utility Routines
- Utility Program Operation
- DBLOAD
- DBRECOV
- >CONTROL
- >EXIT
- >FILE
- >RECOVER
- >ROLLBACK
- >RUN
- DBRESTOR
- DBSTORE
- DBUNLOAD
- DBUTIL
- >>ACTIVATE
- >>ADDINDEX
- >>CREATE
- >>DEACTIVATE
- >>DETACH
- >>DISABLE
- >>DROPINDEX
- >>ENABLE
- >>ERASE
- >>EXIT
- >>HELP
- >>MOVE
- >>PURGE
- >>REBUILDINDEX
- >>REDO
- >>RELEASE
- >>SECURE
- >>SET
- >>SHOW
- Syntax
- Parameters
- Example (Show Users)
- Example Discussion
- Example (Show All)
- Example Discussion
- Example (Show Capacity)
- Format of Show Device List
- Example (Show Device)
- Format of Show Indices
- Example (Show Indices)
- Format of Show Locks List
- Example 1 (Show Locks)
- Example 1 Discussion
- Example 2 (Show Locks)
- Example 2 Discussion
- >>VERIFY
- 9 Using a Remote Database
- 10 Internal Structures and Techniques
- 11 B-Tree Indices
- A Error Messages
- B Results of Multiple Access
- C Database Design Considerations
- D Multiple Calls to DBLOCK
- E TurboIMAGE/XL Log Record Formats
- F MPE/iX Log Record Formats
- G Recovery and Logging Quick Reference
- H TurboIMAGE/XL versus TurboIMAGE/V

Chapter 10 487
Internal Structures and Techniques
Large Size Datasets in TurboIMAGE/iX
Large Size Datasets in TurboIMAGE/iX
Dataset Size Limitations
The IMAGE database management system has been around for more than two decades.
When HP first introduced the product, the maximum size of a dataset was limited to the
MPE file size. However, when users felt the need for much larger dataset sizes, the
'JUMBO' feature was introduced. With this feature, a user can create a dataset with a size
greater than the MPE file size of 4GB. Even though the dataset physically spans across
multiple MPE files called chunk control files and chunkset files, the JUMBO feature allows
them to be seen as a single logical file. Even with this feature, users could only define a
dataset up to 40 GB in size, because of the limit of block numbers, whereas the JUMBO
feature per se doesn't have this restriction. Earlier, IMAGE used to transfer data in blocks,
which necessitated addressing of a record through a block number and an offset within the
block. The maximum number of blocks allowed to be addressed in IMAGE was 2**23 -1,
and the maximum block size was 5120 bytes. The total file size with these, turns out to be
42,949,667,840 bytes (approximately 40 GB). A quick solution has been provided in
IMAGE version C.07.10 released with MPE/iX version 6.0, wherein the limit of 40 GB has
been extended to 80 GB. This was done by increasing the maximum number of blocks to
2**24 -1. The current enhancement lifts the 80 GB restriction by changing the way that
records are addressed internally.
Entryname vs Entrynumber formats
To understand the solution in detail, a brief discussion of the terms entryname and
entrynumber is worthwhile.
As discussed in the beginning of this chapter, a pointer used to point to a record. In
IMAGE, records (entries) were referenced through a 24 bit block number and an 8 bit
offset (slot number) within the block. This format is referred to as 'entryname' format. For
example, the 101st record in a dataset, with a blocking factor of 8, will be referenced as hex
c05, represented as the 24-bit blocknumber of 12 (hex c) and a 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