CRE Programmer's Guide

Run-Time Diagnostic Messages
Common Run-Time Environment (CRE) Programmer’s Guide528146-004
10-3
Trap and Signal Messages
bottom_of_stack
shows the name of the first procedure—the main procedure—of the process in
which the error occurred, the offset within the procedure, and the number of the
code segment in which procedure’s code is located. The stack trace includes all
procedures between
top_of_stack and bottom_of_stack.
The following examples show messages that the CRE might write to the log file:
If a program passes a negative value to a square root function, the CRE writes a
message such as the following to the log file:
\NODE.$Z012:3 - *** Run-time Error 049 ***
\NODE.$Z012:3 - Square root domain fault
\NODE.$Z012:3 - From: DRAWIT + %513, UC.00
\NODE.$Z012:3 - CIRCLE + %21, UC.00
\NODE.$Z012:3 - MYPROG + %7, UC.00
If a program tries to open standard input but the file does not exist, the CRE writes
a message such as the following to the log file:
\NODE.$Z012:3 - *** Run-time Error 059 ***
\NODE.$Z012:3 - Standard input file error (11)
\NODE.$Z012:3 - From: READREC +%54, UC.00
\NODE.$Z012:3 NEXTREC + %15, UC.00
\NODE.$Z012:3 - COMPUTE + %214, UC.00
\NODE.$Z012:3 - MYPROG + %7, UC.00
Note that the error message includes the number of the file-system error number
(11).
If a COBOL program cannot create a new file, the CRE writes a message such as
the following to the log file. Note that the message includes an informational line
that shows the FD-name of the file, the external Guardian file name, and the file’s
status (closed):
\NODE.$Z012:3 - *** Run-time Error 153 ***
\NODE.$Z012:3 - Create of new file failed with error 153
\NODE.$Z012:3 - File FD-IN-FILE = $vol.subvol.file, closed
\NODE.$Z012:3 - From: NEWFILE + %66, UC.00
\NODE.$Z012:3 - PM-ADMIN + %71, UC.00
\NODE.$Z012:3 - MYPROG + %7, UC.00
Trap and Signal Messages
The TNS CRE reports the messages in this subsection if a trap occurs and your
program has neither disabled traps nor enabled its own trap handler. The native CRE
reports the messages in this subsection if a signal is raised and your program does not
have its own signal handler for the signal that was raised. The CRE or run-time library
terminates your program.
The CRE treats trap 4, arithmetic fault, as a program logic error, not a trap. If your
program has disabled overflow traps, the TNS CRE returns control to your run-time
library. The native CRE raises a
SIGFPE signal instead. See the language-specific