COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

Example 321 Input-Output Error Message (CRE)
\DRP12.$:0:622:163577460 - *** Run-time Error 181 ***
\DRP12.$:0:622:163577460 - OPEN operation failed with error 48
\DRP12.$:0:622:163577460 - File BWORK = \DRP12.$DATA4.PTR.GRIP, closed
\DRP12.$:0:622:163577460 - From COBLIB_IO_ERROR_ + 0x660 (DLL zcobdll)
\DRP12.$:0:622:163577460 - COBLIB_OPEN_ + 0x5120 (DLL zcobdll)
\DRP12.$:0:622:163577460 - .BBB + 0x1C0 (UCr)
\DRP12.$:0:622:163577460 - .AAA + 0x90 (UCr)
\DRP12.$:0:622:163577460 - MANE + 0x130 (UCr)
SORT Error Messages
A SORT error message arises from a SORT, RELEASE, or RETURN statement. A SORT error message
is followed by a SORT diagnostic line. For explanation of the SORT diagnostic line, see the FastSort
Manual.
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:
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.
Arithmetic Overflow
Arithmetic overflow means that an arithmetic operation resulted in an arithmetic overflow. Typical
causes include:
• Invalid data is associated with an item, such as an uninitialized USAGE COMPUTATIONAL
or index item.
• A receiving item in an arithmetic statement is too small.
• An intermediate result in a COMPUTE statement exceeds the 36-digit maximum.
SORT Error Messages 1179