iX V6.5 (30391-90011)

680 AppendixH

TurboIMAGE/XL versus TurboIMAGE/V

Status Area

• DBEXPLAIN cannot ﬁnd complete information in the status area for its explanation. To

solve this problem, TurboIMAGE/XL places the missing information in the DBU, which

DBEXPLAIN now references. However, the application must call DBEXPLAIN

immediately after the status information is received. If any other library procedure is

called between the time the error status is returned and DBEXPLAIN is called,

DBEXPLAIN displays the last information stored in the DBU, which may or may not

belong to the library procedure that encountered the error. This could affect

applications that use two or more different status arrays.

Table H-4. compares elements 5 through 10 of the TurboIMAGE/V status area with

elements 5 through 10 of the TurboIMAGE/XL status area. If an error occurs, this

information is returned for all library procedures. If the procedure executes successfully,

this information is returned for DBBEGIN, DBCLOSE, DBCONTROL, DBEND, DBINFO,

DBLOCK, DBMEMO, and DBOPEN.

Table H-4. Status Area Changes for MPE/iX Applications

Element TurboIMAGE/V and Compatibility Mode TurboIMAGE/XL

5 PB-relative address of the caller. 0 (moved to DBU)

6 Bits 7-15: Intrinsic number of called

library procedure.

Bits 0-3: Zero or access mode in which

database is opened.

No change.

7 16-bit address of the database. First 16 bits of the database address.

8 16-bit address of the data set name or

qualiﬁer.

Second 16 bits of database address (data

set or qualiﬁer address moved to DBU).

9 Value of the mode parameter. No change.

10 PB-relative address of the library

procedure or the Compatibility Mode

switch stub.

0 (moved to DBU)