TurboIMAGE/XL Database Management System Reference Manual MPE/iX V6.5 (30391-90011)

Appendix H 673
TurboIMAGE/XL versus TurboIMAGE/V
Overview
For more detailed migration information, refer to the Migration Process Guide.
Table H-1. TurboIMAGE/XL Differences
Area Affected Changes/Additions
Data Set Size – The maximum data set size is 4 gigabytes unless it is a
jumbo data set.
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.
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.
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.
Remote Database Access – Only NS/3000 is supported on MPE/iX.
Roll-Back Recovery – ILR is not required.