C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

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
Checkpoint list inconsistent
Cause
A list of checkpoint item descriptors that the CRE maintains for fault-tolerant processes 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 list. Use a symbolic debugger to help
isolate the problem.
16
Checkpoint list exhausted
Cause
The CRE did not have enough room to store all the checkpoint information required by the
program.
Effect
Program behavior is language and application dependent.
Recovery
Increase the checkpoint list object’s size. For the routine that allocates your checkpoint list, see
the language manual.
17
Cannot obtain control space
Cause
The CRE or a run-time library could not obtain heap space for all of its data.
Effect
If the request came from the CRE, it terminates the program. Otherwise, program behavior is
language and application dependent.
Recovery
You might be able to increase the amount of control space available to your program by reducing
the number of files your program has open at the same time or by decreasing the size of buffers
allocated to open files.
366 Run-Time Messages