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

Appendix B 649
Results of Multiple Access
B Results of Multiple Access
When opening a database with DBOPEN, TurboIMAGE/XL returns information in the
status array describing the results of the procedure call. Figure B-1., “Actions Resulting
from Multiple Access of Databases.” can be used to interpret these results when multiple
processes are using the database.
Each box in Figure B-1. is associated with a requested mode or TurboIMAGE/XL utility
routine identified at the far left of the row in which the box appears. It is also associated
with a possible current access mode or utility routine identified at the top of the column in
which the box appears. The contents of the boxes can be used to determine the results of a
DBOPEN call.
If access is granted, condition code CCE is returned and the first element of the status
array contains a zero. The boxes containing G represent this situation.
If access is not granted, and the reason relates to current database activity, the results are
like those shown in the other boxes. Two types of situations can occur:
• If the first two elements of the status array contain −1 and 0, respectively, the third
element of status will contain a single number. This number is the MPE/iX failure code
returned from the FCHECK intrinsic. See the MPE/iX Intrinsic Reference Manual for
MPE/iX failure code meanings. If that number is 48, 90, or 91, the failure occurred
because current access to the database does not permit it to be opened in the requested
mode. Find the boxes in the requested mode row which contain a number equal to the
third status element. The possible modes and utility routines which other processes
could be using are the ones which label the columns containing these boxes. For
example, if the third status element contains 48 and the requested mode is 2, the
possible current modes are 1 and 5.
To find an alternate mode for accomplishing the task, look down the columns containing
these boxes for one containing a G. If the requested mode labeling the row in which the
G resides can be used, try opening the database with that mode. In the example above,
alternate modes would be 1 or 5 because these rows contain G in columns 1 and 5.
If the box with contents matching the third status element is in a column associated
with a utility, usually the only choice is to wait until execution terminates. When
DBSTORE is being run, it is possible to open the database with mode 6 or 8.
• If the first element in the status array contains −32, the failure occurred because the
root file could be opened but not with the necessary AOPTIONS. This value can also be
returned in situations not related to multiple access. See appendix A in this manual
and the description of the AOPTIONS parameter of the FOPEN intrinsic in the MPE/iX
Intrinsics Reference Manual. Use the same technique described above to determine the
possible current modes or other activity and to select a course of action. For example, if
the requested mode is 2 and the first element of status equals −32, possible current
modes are 4 and 8, and the DBSTORE utility could be executing.
The messages enclosed in quotes are printed when the situation represented by the row