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 483
Internal Structures and Techniques
Dynamic Data Set Expansion
You can select data sets which need dynamic expansion based on anticipated growth.
For new databases, the expansion parameters for data sets can be specified using the
CAPACITY statement of DBSCHEMA as follows:
{ CAPACITY:
C: }
maximum capacity
[(
blocking factor
)] [
,initial capacity
[
,increment
]];
To specify the expansion parameters for data sets of existing databases, use DBChange
Plus, or other third-party tools which support this feature.
In order to use this feature from the user point of view, the only required step is to identify
and enable the data set(s) for dynamic expansion as described above.
When a data set enabled for dynamic expansion is first created, disk space for only the
initial capacity is allocated and initialized. Later when the data set is expanded during
DBPUT, or implied DBPUT for automatic master, additional disk space based on the
increment is allocated and initialized. It can grow up to the maximum capacity specified
for the set. Following the expansion, TurboIMAGE/XL updates various fields related to the
expansion such as current capacity including the expansion and free space counter in the
user label.
The instant when the expansion is triggered and how record addresses are assigned to the
new entry vary in detail data sets from master data sets.
Detail Data Sets
For a detail data set, expansion takes place during DBPUT when the free space counter for
the set is zero. Following the expansion, TurboIMAGE/XL updates the expansion related
fields in the user label such as the end-of-file pointer (high-water mark) and the free space
counter. The expanded data set is perceived as one larger data set and the new record
addresses are assigned using the pointer to delete chain head and the end-of-file pointer
(high-water mark) as done prior to the dynamic expansion feature. The new entry is
assigned the first record address in the expanded area.
Master Data Sets
For a master data set, expansion is triggered when the set is almost full. That is, when the
set has approximated its maximum capacity which will not allow DBPUT to be successful.
For an example, a DBPUT to a detail set with multiple paths to the same automatic master
will require multiple record additions to the automatic master.
Once the expansion is done, the master data set can be perceived as having two areas,
original area and expanded area, managed differently. The original area can have primary
entries and secondary entries, while the expanded area can only have the secondary
entries. Note that the primary capacity (also called hashing capacity or initial capacity),
which is used to calculate the primary address does not change. In essence, the dynamic
expansion results in allocating additional space for secondary entries which implicitly
makes room for additional primary entries in the original area. The primary address of a
new entry is calculated using the value of the entry's key item in the hashing algorithm.
The new entry can reside either at its primary address in the original area, or in the close
vicinity of the primary address in the original area, or in the expanded area. The use of