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 11 513
B-Tree Indices
External Commands and Utilities Affected
NOTE
The length of the argument may not exceed the item length.
DBFIND Arguments
There are two distinct argument styles. The simple argument of the basic DBFIND mode 1
argument is generally interpreted as a sequence of bytes, perhaps containing a wildcard
character.
Another argument style, the structured argument, has been defined for DBFIND modes 4
and 24. This structure allows ranges of item values to be requested, and is explained
below.
DBFIND Structured Argument
The structure of the structured argument for DBFIND modes 4 and 24:
Bytes Meaning
1-2 Type of generic search. An ASCII character pair is in this field:
= search for key values equal to argument1
< search for key values less than argument1
<= search for key values less than or equal to argument1
> search for key values greater than argument1
>= search for key values greater than or equal to argument1
[ ] search for key values greater than or equal to argument1
AND less than or equal to argument2
c. The chain count is the sum of all chain counts (that is, the number of entries in the
super-chain for a B-Tree DBFIND). Record number for the last entry is obtained from the
last entry in the last chain. For first entry, record number of the first entry in the first
chain is obtained. For masters, the chain count reflects the total numberof master entries
qualified, and last entry and first entry values are zeroes.
d. When doing a B-Tree index search, mode-1-style argument is scanned to find the first
occurrence of the wildcard character in the argument text. If the wildcard is not found, a
non-B-Tree index search is done. If the wildcard is found, the rest of the argument text is
ignored. When not doing a B-Tree search (mode is 1 and BTREEMODE1 is OFF, or mode is
10), the entire argument, including any wildcard characters, will be treated as the actual
argument is for a DBFIND mode 1 in releases prior to the release with B-tree index
feature.
e. See "DBFIND Structured Argument" description later in this chapter.
f. For items that are text types (X, U), a B-Tree index search is done if the wildcard is
present in the argument. If the key item is a non-ASCII item, then a B-Tree index find is
not done, and a non-B-Tree index find (mode 1 with BTREEMODE1 is OFF) is done instead.
A programmer can do a B-Tree index find with non-ASCII items by explicitly using
DBFIND modes 4 or 24. (See "DBFIND mode 1-style and non-ASCII keys" below.) This mode
is similar to current TPI mode 21.
g. For detail data set, the halfwords 5-6, 7-8, and 9-10 have 2
31
−1. For master data set, the
halfword 5-6 has 2
31
−1 and 7-8 and 9-10 have zeroes.