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 2 43
Database Structure and Protection
Data Set Types and Relationships
follows all existing entries in the chain. If the path has a sort item, the entry is inserted in
the chain according to the value of that item.
If the entry's sort item value matches the sort item values of other entries in the chain, the
position of the entry is determined by an extended sort field consisting of the sort item
value and the values of all items following the sort item in the entry. If the extended sort
field matches another extended sort field, the entry is inserted chronologically following
the other entries with the same extended sort field value. This also occurs if the sort item
is the last item in the entry and its value matches another entry's sort item value. Note
that Native Language Support does not support extended sort items. The only database
language that supports extended sort fields is Native-3000 which uses US ASCII. If an
extended sort field is used, the sort is done in ASCII collating sequence (negative integers
sort higher than positive).
If you depend on extended sort fields to sort a chain, do not call DBUPDATE to modify any of
the values in the extended sort fields because the chain will not be automatically resorted
according to the new extended sort data values. Instead, call DBDELETE and DBPUT to
re-enter the records with modified values. DBUPDATE only recognizes extended sort items
when the actual search or sort item is changed. Chapter 5 describes DBUPDATE, DBDELETE,
and DBPUT in detail.
If you do not want TurboIMAGE/XL to sort chains by extended sort fields, structure the
data record so that the sort item is in the last field of the record.
When the database content is copied to magnetic tape using the TurboIMAGE/XL utility
program DBUNLOAD, the pointers that define an entry's position in a chain are not copied to
the tape. When the data is loaded back into the database, the chains are re-created.
Therefore, entries that were previously ordered chronologically will not necessarily be in
that same order. The new chronological ordering is based on the order the entries are read
from the tape. The chains of a primary path are an exception; the order of these chains is
preserved if the tape was created with DBUNLOAD in the chained mode. See chapter 8 for
more information about DBUNLOAD.
NOTE
It is important to limit the use of sorted chains to paths consisting of
relatively short chains or chronological sort items that are usually added to
the end of chain (for example, date). Sorted paths should not be used for
multiple key sorts or for sorting entire data sets. These functions are handled
more efficiently by user-written routines or the MPE/iX HP Sort subsystem.
Jumbo Data Sets
You can create data sets greater than 4 GB in size. A data set of this type, called a jumbo
data set, can span more than one MPE file. The naming convention uses POSIX
extensions. For example, a dataset named SALES03 with four multiple files results in a
total of five files with the following names and filecodes:
SALES03 filecode -408
SALES03.001 filecode -409
SALES03.002 filecode -409
SALES03.003 filecode -409
SALES03.004 filecode -409