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 329
Logging and Recovery
Logging Preparation
:LISTLOG
NO LOGGING IDENTIFIERS ASSIGNED (CIWARN 1231)
:GETLOG ORDERLOG;LOG=ORDER001,DISC;PASS=PASSLOG
:LISTLOG
LOGID CREATOR CHANGE AUTO CURRENT LOG FILE
ORDERLOG BEA.MKTG YES NO ORDER001.MKTG.SYS
:ALTLOG ORDERLOG;AUTO
:LISTLOG
LOGID CREATOR CHANGE AUTO CURRENT LOG FILE
ORDERLOG BEA.MKTG YES YES ORDER001.MKTG.SYS
Because NOAUTO is assumed by default in the GETLOG command, the disk log file is closed
when it becomes full and logging is shut down unless you manually issue a CHANGELOG
command. When the NOAUTO default is used, you need to verify the capacity of the log
file on a regular basis and issue a CHANGELOG command when necessary. When the AUTO
option is specified as in the ALTLOG command above, logging automatically initiates a
CHANGELOG command when the current log file becomes full.
In the example above, the AUTO option has been specified. Here is what happens when log
file ORDER001 becomes full. Logging initiates a CHANGELOG command causing the log
records to be written to ORDER002, the next log file in the sequence. As each log file
becomes full, logging initiates additional CHANGELOG commands creating log files
automatically until log file ORDER999 becomes full. At this point, the log file name is reset
to ORDER001 and logging continues automatically.
If you use TurboSTORE/iX 7x24 True-Online Backup (with ONLINE=START or
ONLINE=END) to backup your database and DBRECOV to perform roll-forward recovery,
you must take precautions to synchronize the proper log files with the stored database.
Refer to step 8 for more information.
If you specified the AUTO option as in the preceding example, and you need to restart
logging at logfile001, you can issue an ALTLOG command as shown in the following
example:
:LISTLOG
LOGID CREATOR CHANGE AUTO CURRENT LOG FILE
ORDERLOG BEA.MKTG YES YES ORDER026.MKTG.SYS
:ALTLOG ORDERLOG;LOG=ORDER001,DISC
Step 6--Setting the Log Identifier
The two previous steps were executed using MPE/iX commands. At this point, you must
notify the MPE/iX user logging system of the TurboIMAGE/XL logging intention by setting
the log identifier and logid password into the database root file, using the DBUTIL >>SET
command, as shown in the example below: