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

502 Chapter11
B-Tree Indices
Overview of B-Tree Indices
have keys that satisfy the DBFIND criteria. The total of all
corresponding chains in a detail data set is referred to as a
super-chain. TurboIMAGE/XL fetches each qualifying
master entry in order to determine the total number of
associated detail entries to calculate the sum of the chain
counts. To retrieve all qualified entries in a detail data set
using DBGET, TurboIMAGE "walks" (traverses) this
super-chain.
B-Tree Search is the same as B-Tree DBFIND.
Super-chain is the sum of all detail data set chains involved in the
B-Tree DBFIND.
Trailing-@ Search is a B-Tree search where only the characters left of the @
(wildcard character) of the argument are compared to
qualify an entry. (For example, "cat@" is a trailing-@
search, but "cat@dog" is not and the result will be the
same for both arguments. That is, "dog" will be ignored.)
Wildcard Character refers to a printable ASCII character. The default is @
which means "matches all trailing characters" (unlike "?"
or "#" in MPE terms).
BTREEMODE1 is an option which can be turned ON or OFF using the SET
command of DBUTIL or programmatically using
DBCONTROL. When it is ON, DBFIND mode 1 of an item of X
or U type having a B-Tree index (explicit or implicit), and
having a wildcard character in the argument will result in
a B-Tree search. The ON option allows applications to
benefit from B-Tree indices without modifying
applications. When it is OFF, which is also the default,
DBFIND mode 1 described above works as it did in releases
prior to a release with the B-Tree index feature (C.07.00).
Simple Argument is a DBFIND argument that consists of a sequence of bytes,
as in DBFIND mode 1 argument in releases prior to a
release with the B-Tree index feature (C.07.00). This is
used predominantly for modes 1, 10, and 21. For DBFIND
modes 1 and 21, an X or U type item having B-Tree index
(explicit or implicit) and having the BTREEMODE1 option
ON, the text is scanned for a wildcard character, if any. If a
wildcard is found, DBFIND is treated as a B-Tree DBFIND.
Otherwise, it is treated as DBFIND in releases prior to a
release with the B-Tree index feature (C.07.00).
Structured Argument is a DBFIND fixed format argument construct introduced
with B-Trees enhancement. It is defined as a record
structure, containing search control information as well as
key data. This is used for DBFIND modes 4 and 24, and is
described later in this chapter.