CRE Programmer's Guide

Run-Time Diagnostic Messages
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
10-2
Format of Messages in This Section
•
Spooler Programmer’s Guide
For messages that the CRE reports on behalf of routines that call it, the descriptions
are less precise because the effect on your program and possible recovery actions are
language and application dependent. For more information on errors that are reported
by individual languages, refer to the language reference manual for the routine that
caused the error.
Format of Messages in This Section
This subsection describes the format of the messages the CRE writes to the log file.
Elements surrounded by square brackets (“[” and “]”) are not included in all messages.
process_name
identifies the process in which the error occurred.
nnn
is the CRE message number of the message described in this section.
message
is the text associated with message number nnn.
additional_information
if present, gives more detail about message. For example, if an error occurs when
accessing a file,
additional_information might be the file-system error
number for the error that occurred.
optional_text
if present, provides additional information about the error. For example, it might
show the FORTRAN unit number, or the state of a COBOL file: open, closed, and
so forth. The
optional_text helps you identify the cause of the error message.
top_of_stack
shows the name of the procedure that invoked the run-time library routine in which
the error was detected, the offset within the procedure, and the number of the code
segment in which the procedure’s code is located.
process_name - *** Run-time Error nnn ***
process_name - message [ ( additional_information ) ]
[ process_name - optional_text ]
process_name - From: top_of_stack
process_name - : : : :
process_name - bottom_of_stack