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 7 327
Logging and Recovery
Logging Preparation
Example
:BUILD ORDER001;CODE=LOG;DISC=200000,20,7
Step 5--Creating the Log Identifier
You create the log identifier on MPE/iX by using the GETLOG command shown in this
section. A log identifier (logid) is a unique logical name that identifies a system logging
process to which log records are passed. Before using the GETLOG command, use the
MPE/iX LISTLOG command to check if the logid already exists on MPE/iX. The LISTLOG
command lists all logging identifiers, including creator names, log file names, and whether
or not the AUTO option is used.
If the logid exists and was created by someone else, you must specify a different logid. If
the logid exists and was created by you, check the parameters to verify that they are the
ones you want. If you find, for example, that you used the default NOAUTO option and you
want to change it to AUTO, you can either change it with the MPE/iX ALTLOG command, or
you can release the logid with the MPE/iX RELLOG command and then re-create it with the
GETLOG command. You can release a logid only if you are the creator of that logid.
The logid has a maximum of eight characters. Other users can access the log file and
records in the same log file by using the logid you acquire and its password. To access the
logging system directly through MPE/iX, you must have logging (LG) or operator (OP)
capability and supply the identifier and password on the OPENLOG intrinsic.
If you use logging and create a backup copy using TurboSTORE/iX 7x24 True-Online
Backup (with ONLINE=START or ONLINE=END), you can use either the default
NOAUTO option or use the AUTO option. At database backup time, using TurboSTORE/iX
7X24 True-Online Backup (with ONLINE=START or ONLINE=END), the necessary
information (such as the DBSTORE flag, name of the log file in use, the log record number,
date, and time stamps) is recorded in the database root file before backup. At roll-forward
recovery time using DBRECOV, this information is used to determine the log file to be used
and the position in the log file from where roll-forward recovery must begin. With the
NOAUTO option, there is only one log file. When using the AUTO option, the log file next
in sequence in a round-robin fashion is automatically created. Hence there can be more
than one log file needed for roll-forward recovery. In this case, it is very important to
maintain a process of synchronizing the log files with the backup copy. It is required that
the AUTO/NOAUTO option be not changed after backup and while the log process is
active. You can change it only when starting a new log cycle. Refer to step 8 later in this
chapter.
Syntax
:GETLOG
logid
;LOG=
logfile
, {DISC/TAPE}[;PASS=
password
] [;{AUTO/NOAUTO}]
Parameters
logid is the logging identifier to be established on the system. It consists of a
string of up to eight characters that is meaningful to the user application.