HP 3000 Manuals HP 3000 Manuals
Appendix H TurboIMAGE/XL versus TurboIMAGE/V
Overview
TurboIMAGE/XL is available on the HP 3000 Series 900. This database
management system is very similar to TurboIMAGE/V. However, some
differences exist due to the architecture of the 900 series and the
MPE/iX features of which TurboIMAGE/XL takes advantage. Specific
TurboIMAGE/XL differences are listed here:
* Transaction Management (XM), an internal MPE/iX service, is used
to do the following:
* Ensure intrinsic level physical consistency of the database
as a default unless the AUTODEFER option is enabled.
Incomplete intrinsics will be backed out and not reapplied.
This performs the same functionality as Intrinsic Level
Recovery (ILR) on MPE V.
* Guarantee via Intrinsic Level Recovery (ILR) that not more
than one DBDELETE or DBPUT per process will be lost. ILR
should be disabled on TurboIMAGE/XL.
* Recover transactions via dynamic roll-back recovery while
other database activity is occurring.
* Mapped files are used instead of extra data segments for run-time
control blocks. Another control block, the Database User Local
Index (DBUX), has been added.
* The maximum number of DBOPENs per process is 127 (63 per database)
depending on the availability of system resources.
* Some status area information returned by TurboIMAGE/XL library
procedures is different for MPE/iX applications because of the
change from 16-bit to 32-bit architecture.
* Some information returned by DBINFO mode 402 is different because
of the change in how ILR is implemented.
* For roll-back recovery: If logging to disk, the user log file and
the database must reside in the same volume set. If logging to
tape, the database must be in the system volume set.
* DBSTORE has a TRANSPORT option in the INFO=string for moving
TurboIMAGE/XL databases to MPE V.
[REV BEG]
* Better integrated third-party indexing software that works in
conjunction with TurboIMAGE/XL provides the capability to do
generic key searches, multiple keyword retrievals, and sorted
sequential searches on any database that is enabled for
third-party indexing.
* A logical transaction bracketed by DBXBEGIN and DBXEND can be
dynamically rolled back. This dynamic transaction can be of 1 to
15 databases.
* A data set can be a jumbo set exceeding 4 gigabytes.
* B-tree indices on key items of master data sets allow generic and
range searches on key items of master sets as well as
corresponding detail data set search items.
* Databases can be stored, even when they are open for read/write
access, using TurboSTORE/iX 7x24 True Online Backup (with
ONLINE=START or ONLINE=END option). Their related files, such as
TC file and third-party index files, are stored along with the
databases.
* DBRECOV can perform a roll-forward recovery for a database stored
using TurboSTORE/iX 7x24 True Online Backup (with ONLINE=START or
ONLINE=END option).
* Data sets, master as well as detail, can be dynamically expanded
during DBPUT.
[REV END]
The rest of this appendix discusses the major differences in detail.
They include the following:
* Intrinsic Level Recovery
* Control Blocks
* Status Area
* Moving from MPE/iX to MPE V
TurboIMAGE/XL differences are summarized in Table H-1 .
Moving to TurboIMAGE/XL
To move a database from MPE V to MPE/iX, you need to perform the
following tasks:
1. Disable both ILR and roll-back recovery (use the >>DISABLE command
of DBUTIL).
2. On MPE V, store the database with DBSTORE (or use the MPE V STORE
command).
3. On MPE/iX, restore the database with DBRESTOR (or use the MPE/iX
RESTORE command).
For more detailed migration information, refer to the Migration Process
Guide.
Table H-1. TurboIMAGE/XL Differences
------------------------------------------------------------------------------------------------------
| | |
| Area Affected | Changes/Additions[REV BEG] |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Data Set Size | - The maximum data set size is 4 gigabytes unless it is |
| | a jumbo data set. |
| | |
------------------------------------------------------------------------------------------------------
| [REV END] | |
| | |
| DBEXPLAIN | - Information for DBEXPLAIN is stored in the Database |
| | User Local Control Block (DBU). |
| | |
| | - Calls to DBEXPLAIN must be made immediately after |
| | receiving an error status. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| DBOPEN | - A maximum of 127 DBOPENs is allowed per process (63 |
| | per database). |
| | |
------------------------------------------------------------------------------------------------------
| | |
| DBSTORE Command | - A TRANSPORT option has been added for use when moving |
| | a TurboIMAGE/XL database to MPE V. |
| | |
| | - The move from MPE/iX to MPE V may not be possible if |
| | data sets are larger than the MPE V file size limit. |
| | |
------------------------------------------------------------------------------------------------------
| [REV BEG] | |
| | |
| Dynamic Roll-Back Recovery | - Physical integrity of the database is provided by |
| | MPE/iX Transaction Management (XM) logging, by |
| | default. |
| | |
| | - Dynamic roll-back works in conjunction with XM and |
| | ensures the logical integrity of the database after a |
| | program abort or system failure. |
| | |
| | - Transactions are rolled back online while other |
| | database activity is occurring. |
| | |
| | - Dynamic transaction can span single or multiple |
| | databases. |
| | |
------------------------------------------------------------------------------------------------------
| [REV END] | |
| | |
| Intrinsic Level Recovery | - Physical consistency of the database is provided by |
| | MPE/iX Transaction Management as a default. |
| | |
| | - The ILR log file is replaced by the MPE/iX Transaction |
| | Management log file. |
| | |
| | - Incomplete intrinsics are backed out and will not be |
| | reapplied. |
| | |
| | - DBUPDATE is included in the recovery. |
| | |
| | - DBINFO mode 402 no longer contains ILR recovery |
| | information. |
| | |
| | - To move between MPE V and MPE/iX, disable ILR and |
| | roll-back recovery. |
| | |
| | - ILR is not required for roll-back recovery. |
| | |
------------------------------------------------------------------------------------------------------
Table H-1. TurboIMAGE/XL Differences (cont.)
------------------------------------------------------------------------------------------------------
| | |
| Area Affected | Changes/Additions |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Remote Database Access | - Only NS/3000 is supported on MPE/iX. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Roll-Back Recovery | - ILR is not required. |
| | |
| | - If logging to disk, the user log file and the database |
| | must be in the same volume set. If logging to tape, |
| | the database must be on the system volume set. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Run-Time Control Blocks | - Mapped files are used for control blocks. |
| | |
| | - A control block called the Database User Local Index |
| | (DBUX), which is unique to a process, has been added. |
| | It contains dynamic roll-back information, as well as |
| | the addresses and file numbers of all the DBUs and |
| | DBRs belonging to a specific process. |
| | |
| | - The database ID number returned by DBOPEN now serves |
| | as an index into the DBUX. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Status Area | - Status elements 5, 7, 8, and 10 are modified for |
| | Native Mode (NM) applications. |
| | |
| | - For condition code -9, elements 2, 3, and 4 have a new |
| | format for both Compatibility Mode (CM) and NM |
| | applications. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| TURBO Trace and Profiler | - TURBO Trace and Profiler are not available. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Third-Party Indexing | - If your database is configured for indexing using a |
| | supported third-party product, you have the capability |
| | to do generic key searches, multiple keyword |
| | retrievals, and sorted sequential searches on that |
| | database using the DBFIND and DBGET intrinsics. Refer |
| | to your third-party vendor documentation for details. |
| | |
------------------------------------------------------------------------------------------------------
| [REV BEG] | |
| | |
| B-Tree Indices | - If a B-tree index exists on the key item of the |
| | master, allows you to do generic and range searches |
| | using this key item, or search items of its |
| | corresponding detail data sets. DBFIND can be used |
| | both for master and detail. New feature for |
| | TurboIMAGE/XL; not in TurboIMAGE/V. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Master and Detail Data Set | - Data set can be expanded dynamically according to |
| Expansion | capacity expansion parameters. New feature for |
| | TurboIMAGE/XL; not in TurboIMAGE/V. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Jumbo Data Sets | - Allows you to create data sets greater than 4 |
| | gigabytes. New feature for TurboIMAGE/XL; not in |
| | TurboIMAGE/V. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Dynamic Multiple Database | - This is an extension of the dynamic transaction for a |
| Transaction (DMDBX) | single database. The dynamic transaction can span |
| | 1-15 databases. New feature for TurboIMAGE/XL; not in |
| | TurboIMAGE/V. |
| | |
------------------------------------------------------------------------------------------------------
| | |
| Deadlock Detection | - Database can be activated for deadlock detection to |
| | avoid system hangs. New feature for TurboIMAGE/XL; |
| | not in TurboIMAGE/V.[REV END] |
| | |
------------------------------------------------------------------------------------------------------