FORTRAN Reference Manual

Run-Time Diagnostic Messages

FORTRAN Reference Manual—528615-001

G-18

Run-Time Core Messages

Recovery. The program might have written data in the upper 32K words of the user

data segment. The upper 32K words are reserved for run-time library data. Check the

program’s logic. Use Inspect to help isolate the problem or consult your system

administrator.

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.

Effect. The run-time 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

runtime 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 Inspect to help isolate the problem. For details of how to determine where the

program overwrites G[0], see Using Inspect on page 11-10.

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 run-time 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, provided that doing so will not duplicate

operations already performed, such as updating a database a second time.

Cause. A list of checkpoint item descriptors that the run-time maintains for NonStop

processes was invalid.

Effect. The run-time 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 Inspect to help isolate the problem.

MCB pointer corrupt

Premature takeover

Checkpoint list inconsistent