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

Binder Messages
Binder Manual—528613-004
8-2
Error Messages and Warnings
Binder assigned an arbitrary name after other file-naming attempts failed for the target
file. nnnn is a numerical suffix that uniquely identifies the file. vol and subvol are the
same as would have been used. This is an informative message only.
1
You cannot specify an OWN (SAVE) block separately from its associated code block.
Adding, replacing, or deleting the code block automatically adds, replaces, or deletes
the own block.
2
These commands cannot refer to a COBOL85 PUCB by name. Although a COBOL85
PUCB is not classified as an OWN block, Binder treats it the same as an OWN block in
ADD, REPLACE, and DELETE commands
3
You cannot specify an ALTER option more than once in a command line.
4
Callable procedures must also be privileged code; Binder automatically sets PRIV ON
if you specify CALLABLE ON. PRIV OFF is overridden in this case.
5
The object file must be in the standard Binder format. If the code was produced by an
earlier, incompatible version of the compiler, you must recompile. (An older version of
Binder also displays this message if it attempts to process a new object file produced
by a later version of Binder.)
E ADD/REPLACE/DELETE may not be used on OWN (SAVE)
blocks
E ADD/REPLACE/DELETE may not be used on PUCB blocks
E ALTER specification reused
W Alter to CALLABLE and not PRIV means CALLABLE and
PRIV: entry-point-name
E Bad object file format version: file-name