CRE Programmer's Guide

Run-Time Diagnostic Messages
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
10-7
CRE Service Function Messages
13
Cause. The pointer at location G[0] of the program’s user data segment 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.
In the native environment, this error can occur if the MCB run-time data structure has
been corrupted.
Effect. The CRE attempts to restore the pointer at G[0] 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. Check the program’s logic to see if it overwrote the MCB pointer at G[0].
Use a symbolic debugger appropriate for the type of code to help isolate the problem.
See Using the Inspect, Native Inspect, and Visual Inspect Symbolic Debuggers With
CRE Programs on page 2-62 for details of how to determine where the program
overwrites G[0].
14
Cause. The CRE backup process received an operating system 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.
Effect. The CRE invokes PROCESS_STOP_, specifying the ABEND variant and the
text “Premature takeover.”
Recovery. If the takeover occurred because of faulty program logic, correct the
program’s logic. If the takeover occurred for other reasons, such as a hardware failure,
you might want to rerun the program. Do not rerun the program if doing so will
duplicate operations already performed, such as updating a database a second time.
15
Cause. A list of checkpoint item descriptors that the CRE maintains for process pairs
was invalid.
Effect. The CRE terminates the program.
Recovery. The list of items to checkpoint is maintained in the program’s address
space. Check the program’s logic. The program might have overwritten the checkpoint
MCB pointer corrupt
Premature takeover
Checkpoint list inconsistent