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

530 AppendixA
Error Messages
Library Procedure Error Messages
Abort Conditions
In general, four types of error conditions can cause TurboIMAGE/XL to abort the calling
process:
1. A call from a Compatibility Mode user process with the hardware DB register not
pointing to the process stack.
2. A structurally damaged database.
3. An internal error in an MPE file intrinsic which the calling procedure cannot correct.
4. An internal inconsistency in the database or the DBG, DBB, or DBU discovered by a
library procedure.
In case 1, the procedure prints the standard MPE run-time abort message. In cases 2, 3,
and 4, TurboIMAGE/XL prints additional information on the standard list device about
the error prior to printing the standard MPE abort message. The first line of this
information is:
ABORT: procedure name ON DATABASE name;
where procedure name is the name of the library procedure which caused the abort and
name is the name of the database being accessed at the time of the abort. "Library
Procedure Abort Condition Messages" describes additional lines of information which
could appear prior to the standard MPE abort message.
Some of the abort conditions are due to an error in one of the MPE file intrinsics FOPEN,
FREADLABEL, FREADDIR, FWRITELABEL, FWRITEDIR, or FCLOSE. Aborts of this type
generally occur after the procedure has possibly altered the database so that the database
structure has been damaged in some way. Each of the messages in the section entitled
"Library Procedure Abort Condition Messages," which refer to a TurboIMAGE/XL data
file, are followed by an MPE file information display listing all of the characteristics of the
MPE data set or root file where the error occurred, along with an MPE error number.
I and J Files
When TurboIMAGE/XL detects an internal inconsistency or other abnormal situation and
the database is enabled for dumping, it can create special "I" and "J" files before it
terminates. The "I" file consists of the user's stack and procedure call trace markers; the
"J" file consists of the TurboIMAGE/XL database control blocks. TurboIMAGE/XL only
creates these "I" and "J" files if a database user has run DBUTIL and specified ENABLE
database name FOR DUMPING. So, if you want "I" and "J" files, you must specifically
request them through this DBUTIL command. Note that "I" and "J" files are useful for
debugging only if the database is known to be structurally sound.