COBOL Manual for TNS and TNS/R Programs

ManualsBrandsHP ManualsServerHP NonStop G-Series

1861

Run-Time Diagnostic Messages

HP COBOL Manual for TNS and TNS/R Programs—522555-006

48-7

Guardian Abnormal Termination Messages

A Guardian abnormal termination message results from circumstances that cause the

Guardian environment to terminate the execution of a run unit. The operating

environment delivers its own message—the Guardian abnormal termination

message—after (or instead of) delivering a COBOL run-time diagnostic message. A

Guardian abnormal termination message is more cryptic than a COBOL run-time

diagnostic message.

Here is a typical Guardian abnormal termination message in the non-CRE

environment:

INSPECT - SYMBOLIC DEBUGGER - T9673C00 - (10JUL89)

INSPECT P=000102, E=000350 -TRAP 2- ( arithmetic overflow )

*175,09,028* PRODXXX #X + %77I

_PRODXXX_

Here is a typical Guardian abnormal termination message in the CRE:

ABENDED: 10,355

CPU time: 0:00:00.005

3: Premature process termination with fatal errors or

diagnostics

The run unit was operating in an environment with traps armed, and an arithmetic

overflow occurred. The Guardian environment placed the job into the selected

debugger. You can use the “#X + 77I” information to find out where in the source

program the problem arose.

The three most common causes of Guardian abnormal termination messages are:

•

Abend (abnormal termination)

•

Arithmetic Overflow

•

Stack Overflow

These topics explain abnormal termination messages and describe what to do if they

occur.

Abend

Abend is short for “abnormal end.” It follows any fatal error message that the run-time

routines generate. If it appears without a run-time diagnostic message, you might want

to execute the run unit again with the SAVEABEND attribute set so that the selected

debugger makes a save file. You might also want to recompile with SYMBOLS and

INSPECT directives, and then execute with SAVEABEND so that you can make easier

use of the save file.