COBOL Manual for TNS and TNS/R Programs

Run-Time Diagnostic Messages
HP COBOL Manual for TNS and TNS/R Programs522555-006
48-21
Message List
Recovery. If the program was compiled with the COBOL85 compiler, check the
program’s logic to see if it overwrote the MCB pointer at G[0]. Use the selected
debugger to help isolate the problem.
If the program was compiled with the NMCOBOL compiler: In a native object, the MCB
is not at a fixed location. To find it, use the noft command EXTSYMTBL. Then use the
selected debugger to help isolate the problem. The noft output can be very lengthy.
Example 48-4 shows the location of the MCB for the native object file DOMS1400 is
0x0800e3e0.
14 (none)
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.
Effect. The CRE calls 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, provided that doing so will not duplicate
operations already performed, such as updating a database a second time.
15 (none)
Cause. A list of checkpoint item descriptors that a run-time library or CRE maintains
for fault-tolerant processes was invalid.
Effect. The run unit terminates abnormally.
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 the selected debugger to help isolate the problem.
Example 48-4. Using noft to Find the MCB Pointer in a Native Object File
noft> FILE DOMS1400noft> EXTSYMTBL
....
4 0 _MCB 0x0800e3e0 Glob
....noft>
Premature takeover
Checkpoint list inconsistent