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

94 Chapter4
Using the Database
Opening the Database
Database Control Blocks
TurboIMAGE/XL executes using data stored in different types of control blocks stored in
privileged mapped files or virtual data objects: the Database System Control Block (DBS),
the Database Globals Control Block (DBG), the Database Buffer Area Control Block
(DBB), the Database User Local Control Block (DBU), the Remote Database Control Block
(DBR), Database User Local Index Control Block (DBUX), the Lock Table (TURBOLKT),
Global Dynamic Multi-database Transaction Table (TURBOGTX), DBQUIESCE and DBOPEN
Table (QOPEN), and DBQUIESCE Lock Table (QLOCK). These are described below:
• The Database System Control Block (DBS) is created by DBOPEN if it does not already
exist. The DBS is used as a system-wide table to locate the current Database Globals
Control Block (DBG) for any opened database. Each system has only one DBS, created
as a permanent file called TURBODBS in the PUB group and the SYS account on that
system.
• The Database Globals Control Block (DBG) is created for a particular database when
the first user's process calls the DBOPEN procedure to open the database. The DBG
contains global information required by TurboIMAGE/XL intrinsics during run-time,
including a pointer to the Database Buffer Area Control Block (DBB). Each open
database has exactly one DBG regardless of the number of concurrent access paths to
the database. All TurboIMAGE/XL procedures on a particular database (except
DBERROR and DBEXPLAIN) reference the DBG. In addition, the DBG contains the lock
table which holds user-level locking information. The DBG is purged when the last
user's process closes the database (DBCLOSE).
• The Database Buffer Area Control Block (DBB) is created for a particular database
when the first user's process calls the DBOPEN procedure to open the database. The DBB
contains a set of buffer headers which point to data in memory from any of the data
sets, and contains a pointer to the DBG. Global information regarding logging and
recovery is also contained within the DBB. The DBB is used to retrieve, log, and update
data located in the data set files on disk. The DBB is purged when the last user closes
the database (DBCLOSE).
• One Database User Local Control Block (DBU) is created each time a user's process
successfully calls DBOPEN. Each DBU contains information about the user's individual
access to the database and contains pointers to the DBS, DBG, and DBB. The privileged
mapped file containing the DBU is associated with this DBOPEN. The DBU is purged
when the corresponding DBCLOSE closes the database. A process can open a maximum
of 127 databases (or one database 63 times), depending upon the system resources;
therefore, a maximum of 127 DBUs can be created. It is recommended that a process
close a database once it is no longer needed for that process.
• One Remote Database Control Block (DBR) is created on the local system each time a
user's process successfully opens a remote database. The DBR contains database set
and item information as well as the work areas necessary to set up communications to
the remote computer.
• The Database User Local Index Control Block (DBUX) is created the first time the
user's process calls DBOPEN. One DBUX exists for each user's process. Its purpose is to
keep track of the addresses of all the DBUs and/or DBRs for that process. Because a
maximum of 127 entries are allowed in the DBUX, each process is allowed 127 DBOPENs