COBOL Manual for TNS/E Programs (H06.03+)

Run-Time Diagnostic Messages
HP COBOL Manual for TNS/E Programs—520347-003
48-9
Message List
12
Cause. The CRE or run-time library detected a logic error within its own domain. For
example, although each data item it is using is valid, the values of the data items are
mutually inconsistent.
Effect. The CRE calls PROCESS_STOP_, specifying the ABEND variant and the text
“Logic error.”
Recovery. To correct the problem, initialize uninitialized pointers.
13
Cause. The pointer at symbolic location _MCB to its primary data structure—the
Master Control Block (MCB)—does not point to the MCB. Both the CRE and run-time
libraries can report this error.
Effect. The CRE attempts to restore the MCB pointer and to write a message to the
standard log file; however, because its environment might be corrupted, the CRE might
not be able to log a message. In that case, it calls PROCESS_STOP_, specifying the
ABEND variant and the text “Corrupted Environment.”
Recovery. In a native object, the MCB is not at a fixed location. To find it, use the
enoft command EXTSYMTBL. Then use the selected debugger to help isolate the
problem. The enoft output can be very lengthy. Example 48-2 shows the location of
the MCB for the native object file DOMS1400 is 0x0800e3e0.
14
Cause. The backup process received a Guardian message that it had become the
primary process, but it had not yet received all of its initial checkpoint information from
its predecessor primary process.
Logic error
MCB pointer corrupt
Example 48-2. Using enoft to Find the MCB Pointer in a Native Object File
enoft> FILE DOMS1400
enoft> EXTSYMTBL
....
4 0 _MCB 0x0800e3e0 Glob
....
enoft>
Premature takeover