These run-time errors indicate that the process detected an integrity error within the body of the database.
Verify the error using the MUPIP command INTEG SUBSCRIPT=, specifying an immediate ancestor node of the global variable displayed in the error message. Alternatively, you may try the access by running the same routine in another process or by using Direct Mode to perform the same actions as those performed by the M line that triggered the error. If you cannot reproduce the error, refer to section P1.
Most of these errors terminate with a four-character failure code. Each character in the code represents the failure type for an attempt to perform the database access. In cases where the letters are not all the same, the last code is the most critical, because it reflects what happened when the process made its last retry. Earlier tries show error codes that are important to establishing the context of the last error.
The following table lists the failure codes, whether or not they require a MUPIP INTEG, a brief description of the code's meaning, and a section reference for locating more information.
|
Run-Time Database Failure Codes |
|||
|
FAIL CODE |
RUn INTEG |
DESCRIPTION |
SECTION |
|
A B C D E |
x x x x |
Special case of code C. Key too large to be correct. Record unaligned: properly formatted record header did not appear where expected. Record too small to be correct. History overrun prevents validation of a block. |
O2 K1 O2 O2 R3 |
|
G H* J K L |
- x |
Cache record modified while in use by the transaction. Development of a new version of a block encountered an out of design condition. Level on a child does not show it to be a direct descendent of its parent. Cache control problem encountered or suspected. Conflicting update of a block took priority. |
R3 P1 O1 C1 R3 |
|
M N O P Q |
x x |
Error during commit that the database logic does not handle. A primitive such as a file or queue operation failed. Before image was lost prior to its transfer to the journal buffer. Multi-block update aborted - database damage likely. Shared memory interlock failed. |
P1 R7 R3 I5 R7 |
|
R S U V X |
x |
Critical section reset (probably by DSE). Attempt to increase the level beyond current maximum. Cache record unstable while in use by the transaction. Read-only process could not find room to work. Bitmap block header invalid. |
R5 R8 R3 R9 M2 |
|
Y Z a b c |
x x |
Record offset outside of block bounds. Block did not contain record predicted by the index. Predicted bitmap preempted by another update. History overrun prevents validation of a bitmap. Bitmap cache record modified while in use by the transaction. |
02 02 R3 R3 R3 |
|
d e f g |
x |
Not currently used. Attempt to read a block outside the bounds of the database. Conflicting update took priority on a non-isolated global and a block split requires a TP_RESTART. The number of conflicting updates on non-isolated global nodes exceed an acceptable level and requires a TP_RESTART. |
- 02 R3 R3 |
![[Note]](images/note.png)
|
|
|
*Indicates a process problem |