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 3 73
Defining a Database
Set Part
the data set, or is zero, but the initial capacity is greater than zero, then
the increment for each expansion is defaulted to ten percent (10%) of the
initial capacity for the data set. If the initial capacity is equal to the
maximum capacity, or the initial capacity is zero, then this indicates the
data set cannot be expanded and increment is ignored.
Examples
NAME: SUP-MASTER,MANUAL /INDEXED (13/12,18),DISC1;
ENTRY: SUPPLIER(1),
STREET-ADD,
CITY,
STATE,
ZIP;
CAPACITY: 2001,501,20%;
Description
The example also shows the data set SUP-MASTER which will reside on Disc1. Assigning
the device class where a data set will reside can provide greater performance for the
TurboIMAGE/XL database and can aid in better use of system resources. An
understanding of how to spread the data sets over multiple disk devices can be obtained
from your system manager. Your system manager will be able to give you a listing of logical
devices and their corresponding device class names (each logical device can have up to
eight names).
To retrieve information on where each data set resides after specifying device classes in
the schema, you can use the MPE/iX command LISTF,3 (after the database is created).
This command lists the device type, logical device number, and the device class name for
each data set in the database. The DBUTIL >>SHOW command can also be used to display
the devices on which data sets reside.
The data set SUP-MASTER will have a B-Tree index created on the key item, SUPPLIER.
B-Tree DBFINDs can be done using SUPPLIER for SUP-MASTER. Also, B-Tree DBFINDs
will be allowed using all of its corresponding search items in the detail sets. In the above
example, SUPPLIER has only one path. Hence, B-Tree DBFIND can be done using the
related search item and the detail data set. The presence of capacity expansion parameters
indicate that it is enabled for dynamic data set expansion.
The example also shows that the maximum capacity is 2001, the initial capacity is 501,
and the increment is 20%.
Another example is capacity defined as follows:
CAPACITY: 2001,501,25;
The maximum capacity is set at 2001, has an initial capacity of 501, and will be
automatically expanded by 25 when the initialized space is exhausted.
To allow dynamic expansion for a master data set, specify the maximum capacity and the
initial capacity when defining the data set. If dynamic expansion is not needed for the data
set, the maximum capacity is the only required parameter.
Verify that there is enough disk space for a data set to be expanded. Performance may be
impacted by the number of entries incremented when a master data set is dynamically
expanded. The number of disk extents used for the data set file may also impact the