COBOL Manual for TNS and TNS/R Programs

Creating and Compiling HP COBOL Source
Programs
HP COBOL Manual for TNS and TNS/R Programs—522555-006
22-52
Diagnostic Messages
Binder Messages
A Binder message begins with one of these strings:
**** Binder WARNING nnn ****
**** Binder ERROR nnn ****
**** Binder FATAL ERROR nnn ****
(where n is a digit). For information about specific Binder messages, see the Binder
Manual.
Error Files
The compiler directive ERRORFILE causes the compiler to document its warning and
error messages in an error file. For each compiler warning or error message, the
compiler writes one record to the error file. Each record contains this information:
•
The fully qualified, local file name of the source file in which the warning or error
occurred
If you specified a DEFINE name for the name of the source file, then this entry is
the file name that the DEFINE produced.
•
The line number that the HP editor (EDIT or TEDIT) assigned to the line in which
the warning or error occurred
•
The column number in which the warning or error occurred
•
The warning or error message text
The error file is not an EDIT file; it is of type 106. You can use it only with the TACL
macro FIXERRS. For information about the FIXERRS macro, see FIXERRS Macro.
In this example, the error file is ERRORS on the default volume and subvolume:
90> COBOL85 /IN XYZ, OUT $SPX/ XYZOBJ; ERRORFILE ERRORS
90> NMCOBOL /IN XYZ, OUT $SPX/ XYZOBJ; ERRORFILE ERRORS
If the file ERRORS does not exist, the compiler creates an entry-sequenced file of type
106 and names it ERRORS. If ERRORS does exist, and is of type 106, the compiler
replaces its contents with the new error file. If ERRORS exists but is not of type 106,
the compiler terminates with the message:
ERRORFILE not created