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

112 Chapter4
Using the Database
Updating Data
NOTE
To avoid locking around terminal reads, you may need to establish the lock,
perform a mode 1 DBGET, check the value, update the entry, then remove the
lock.
The password you use to open the database must grant update capability to the data items
you intend to change. The user class number associated with the password must either be
in the write class list of the data set containing the items to be updated, or in both the read
class list of the data set and in the write class list of the data item.
Updating Key, Search, and Sort Items
For compatibility and security reasons, by default you cannot use the DBUPDATE library
procedure to update a master data set key item, or a detail data set search or sort item.
However, in database access mode 1, 3, or 4, you can update search or sort items if
permitted by the CIUPDATE option settings for the database and the current process; refer
to the following discussion of CIUPDATE. If you do not or cannot take advantage of the
CIUPDATE option and need to change search or sort items, or if you need to change master
data set key items, you can first delete the selected entry with DBDELETE (see the section
entitled "Deleting Data Entries"), and then add the entry back into the database with
DBPUT. However, keep in mind that this method places the new record at the end of each
unsorted chain, which disturbs the chronological order of each path.
The new entry must be complete. That is, you cannot delete an entry and then add a new
entry with only the item you want changed. If you do this, the rest of the entry will be set
to binary zeros by DBPUT. Furthermore, make sure the current list is truly current when
using an asterisk (*) to reference the list; otherwise, if items have been added or deleted,
you could cause DBPUT to write binary zeros over existing data. Note that using the
commercial "at sign" (@) to write all the items in a data entry avoids this problem.
To facilitate updates of detail data set critical items, you should design any new databases
to take advantage of the CIUPDATE option. Applications to be used with these databases
can be written as described in the next section.
Critical Item Update
TurboIMAGE/XL provides an option called critical item update (CIUPDATE) which,
depending on the settings for the database and the current process, can permit you to
update the values of detail data set search and sort items. To take advantage of this option,
you first need to set it through the TurboIMAGE/XL utility DBUTIL. Use the DBUTIL >>SET
command, and set the CIUPDATE option equal to ON or ALLOWED.
NOTE
The default setting is now ALLOWED. It was DISALLOWED in releases before
C.07.00.
The ON setting permits any process to use critical item update on the database unless the
process explicitly disables the option by calling the DBCONTROL procedure in mode 6; this
call disables the option for the duration of the process or until a call to DBCONTROL in mode
5 enables the option. The ALLOWED setting requires that a process first call DBCONTROL in
mode 5 to enable the CIUPDATE option for the duration of the process or until a call to