TurboIMAGE/XL Database Management System Reference Manual (30391-90012)

Appendix H 689
TurboIMAGE/XL versus TurboIMAGE/V
Status Area
Status Area
All addresses on MPE/iX are 32 bits. This has necessitated a change in some of the
information returned in the status area by TurboIMAGE/XL library procedures.
Major Differences
Because TurboIMAGE/XL uses MPE/iX mapped files, DBOPEN calls HPFOPEN to open these
mapped files. If an error occurs during this process, the condition code −9, formerly used to
indicate an MPE/iX GETDSEG failure, is now used to indicate an MPE/iX HPFOPEN failure.
DBOPEN returns the HPFOPEN status in the status array as shown in Table H-3.
When DBOPEN is successful, elements 3 and 4 still contain the size, in halfwords, of the
DBG and DBU respectively. However, because the maximum value that can be reported is
32,768 halfwords (65,536 bytes), if the DBG or the DBU/DBR is larger than that, only
32,768 halfwords are reported in the status area. Note that although on MPE/iX words are
32-bit words, TurboIMAGE/XL still returns all lengths in the status area as the number of
16-bit halfwords.
For applications in Compatibility Mode (CM):
• Switch stubs translate the information returned to the status area by TurboIMAGE/XL.
After translation, each element of the status area contains the information expected by
TurboIMAGE/XL applications with one exception. Element 10 contains the relative
address of the switch stub rather than that of the actual library procedure (intrinsic).
For applications in Native Mode (NM):
• On TurboIMAGE/XL, elements 5 and 10 of the status area do not contain code offsets
because they are now 32 bits. Halfwords 5 and 10 return 0.
• Halfwords 7 and 8 contain the 32-bit address of the database parameter.
Table H-3. Condition Code -9 Status Array
Element Content
1 −9
2 Control Block Code
DBG = 1
DBU = 2
DBR = 3
DBS = 4
DBUX = 5
3 HPFOPEN File System Error (16 bits)
4 File System Intrinsic Code