Four bytes of the DB trace information contain task-specific DB return codes (see the openUTM manual "Messages, Debugging and Diagnostics in BS2000", DB-DIAGAREA). These codes are version-dependent and are only applicable to that version alone.
The return codes have the following structure: abcd
a contains:
X’04’ | Error in eventing (ENABLE) |
X’08’ | Serialization error |
X’0C’ | Error in eventing |
X’10’ | LINK error |
X’14’ | Communication pool no longer contains enough free space |
X’18’ | Internal error in UDSCON |
X’1C’ | Memory error |
X’20’ | Unknown keyword |
X’24’ | START parameters not valid for UDS/SQL |
X’28’ | Length input in START parameters is 0 |
X’2C’ | DMS error returned to status query |
X’30’ | No application ENTRY available |
X’34’ | Addressed application ENTRY missing |
X’38’ | Communication pool closed normally |
X’3C’ | Communication pool closed abnormally |
X’40’ | Unrecoverable error in memory administration |
X’44’ | Error in status message |
X’48’ | Status of transaction ambiguous |
X’4C’ | Error in FORWARD eventing |
X’50’ | Violation of security requirements |
X’54’ | Error in program management |
X’58’ | Error in result transfer |
X‘5C‘ | Task deadlock in TIAM application |
X‘60‘ | Error in transfer data |
b contains:
Additional information for diagnostics purposes (for some errors)
c contains:
Additional information for diagnostics purposes (for some errors)
In some error situations which are already isolated sufficiently by d, additional information is provided for diagnostic purposes in abc.
d contains:
X’00’ | Function executed without error |
X’04’ | Invalid operation code |
X’08’ | Internal error (see meaning under a) |
X’0C’ | No connection to UDS/SQL subtasks |
X’10’ | UDS/SQL terminated |
X’14’ | Transaction does not exist (any more) |
X’18’ | Transaction terminated abnormally |
X’1C’ | Transaction could not be opened due to lack of tables |
X’20’ | Transaction termination fails |
X’24’ | Error in START parameter |
X’28’ | Errored termination of a PTC transaction |
X’2C’ | Processing error |
X’30’ | 2nd PTC from user |
X’34’ | User error in CALL DML |
X’38’ | Processing error during FINISH |
X’3C’ | Processing error during FINISH WITH CANCEL |
X’40’ | Error returned to status query |
X’44’ | Unrecoverable CALL DML error |
X’48’ | READY error in KDBS |
X’4C’ | No connection possible - all channels occupied |
X’50’ | Invalid communication name |
X’54’ | Addressed communication pool does not exist |
X’58’ | Communication pool not fully created yet |
X’5C’ | Task does not exist for which an asynchronous CANCEL has been attempted |
X’60’ | Channel active |
X’64’ | Start BIB: User requests connection |
X’68’ | Stop BIB: User requests connection cleardown |
X’6C’ | User already connected with UDS/SQL |
X’70’ | Versions of the UDS/SQL modules mixed |
X’74’ | Error in distributed processing |
X’78’ | Illegal BS2000 version |
X’7C’ | Subschema change during a transaction |
X’80’ | Serialization error |
X’84’ | User’s own task cannot be aborted asynchronously |
X’88’ | No BREAK TA precedes CONTINUE TA |
X’8C’ | User entered invalid parameters |
X’90’ | Deadlock |
X’94’ | READY for transaction missing |
X’98’ | Unrecoverable error in open PST |
X’9C’ | Error in master task message |
X’A0’ | Error in update recognition |
X’A4’ | PETA only possible for update transaction |
X’A8’ | SQL conversation could not be opened due to lack of tables |
X’AC’ | No SQL OUTPUT could be created |
X’B0’ | SQL not available in loaded DBH |
X’B4’ | Length in the conversation memory changed incorrectly |
X’B8’ | UDS/SQL not addressable in AMODE3 |
X’BC’ | Application and AMODE not compatible |
X’C0’ | Call not permitted in secured UDS/SQL configuration |
X’C4’ | Illegal module library |
X’C8’ | No connection to UDS/SQL configuration possible |
X’CC’ | Inconsistent DML request |