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

154 Chapter5
TurboIMAGE/XL Library Procedures
DBDELETE
Database" in chapter 4 for what to consider when enabling or disabling this option.
If the process is logging, a call to DBDELETE causes a log record to be written with such
information as the time, date, user identification number, and a copy of the record to be
deleted. In a dynamic transaction, DBDELETE causes a log record to be written after the
physical transaction has been successfully completed. If DBDELETE cannot complete within
a dynamic transaction, an error is returned. This error condition must be checked, and you
must decide to use DBXUNDO, DBXEND, or continue with the remainder of the dynamic
transaction. DBXUNDO will abort the entire transaction. DBXEND will terminate the dynamic
transaction; the modifications completed thus far within the transaction will remain in the
database.
Table 5-8. DBDELETE Return Status Values
File System, Memory
Management, and
Transaction Management
Failures:
-1 FOPEN failure.
-3 FREADDIR failure.
-4 FREADLABEL failure.
-5 FWRITEDIR failure.
-6 FWRITELABEL failure.
-167 Cannot begin MPE XL XM transaction: XM error
nn .
-168 Cannot attach n to MPE XL XM: file system error
nn .
-169 Invalid mode for XM attach options.
-175 Cannot attach n to MPE XL XM: XM error nn .
-176 Cannot detach n from MPE XL XM: XM error nn .
-178 Cannot detach n from MPE XL XM: file system
error nn .
-199 Cannot end MPE XL XM transaction: XM error nn .
-209 Invalid mode for XM detach options.
Calling Errors: -11 Bad database reference.
-12 No lock covers the data entry to be deleted. (Occurs
only if database open in access mode 1.)
-14 Illegal intrinsic in current access mode.
-21 Bad data set reference.
-23 Data set not writable.
-24 DBDelete not allowed on Auto Master.
-31 Bad mode.
-222 Only DBXUNDO allowed when a dynamic
transaction encounters an error.