Binder Manual (G06.27+, H06.04+, J06.03+)

Binder Manual—528613-004
8-1
8 Binder Messages
This section lists three types of messages returned by Binder: error messages,
warnings, and completion codes.
Error Messages and Warnings
This subsection lists Binder error and warning messages in numerical order. The listing
includes a description of the possible sources of the error and the corrective action you
can take.
The Program Development Tools (PDT)—that is, Binder, Crossref, and Inspect—all
have the error file called PDTERROR associated with them. This file must reside on
the same volume and subvolume as the PDT products. As part of the standard RVU,
they reside on $SYSTEM.SYSTEM. If you choose to relocate the PDT products on
some other volume or subvolume, you must also relocate PDTERROR and PDTHELP.
When Binder detects an error condition, it searches PDTERROR for the corresponding
error message (documented in this section). If PDTERROR is missing, Binder displays
a cryptic message of the form
BINDER ERROR nn
and warns you that the error file is missing.
All Binder error messages are qualified by a letter representing their severity code.
These codes and their meanings are as follows:
This message precedes other information about a Binder internal consistency error; a
stack trace usually accompanies the message. If you receive this message, contact
your HP representative.
Topic Page
Error Messages and Warnings
8-1
Completion Codes 8-28
Code Meaning
W Warning. Binder issues a WARNING but still produces an
object file.
E Error. Binder returns to the Binder prompt without completing
the current operation.
F Fatal Error. Binder terminates without producing an object file.
F Internal error at P=% nnnnnn text
W Object file is named $ vol. subvol.ZZBI nnnn