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

Binder Messages
Binder Manual—528613-004
8-3
Error Messages and Warnings
6
No code or data block by the given name was found in the specified object file. You
can check block names by using the LIST LOC command or by referring to a current
compiler listing. You can ensure that Binder searches the correct file by giving the file
name on the command or by using the FILE command.
7
The range of the data block specified in the DUMP or MODIFY command is not
completely initialized. Binder compresses uninitialized data out of the target file.
Therefore, it cannot be displayed.
8
The block specified in a MODIFY command is not in the include list (code or data)
indicated by the command.
9
The CHECK BLOCK parameter (SELECT command) is set ON, and common or global
declarations are inconsistent in length or addressing mode. The data block reference is
unresolved. You can correct the inconsistency or use SELECT CHECK BLOCK OFF to
allow resolution. (The INFO UNRESOLVED * command displays unresolved code and
data blocks.)
The additional text indicating which blocks are compared can have two forms. If you
are using Binder interactively, the text indicates which object files Binder gets the data
blocks from. If you are compiling a program, the text indicates which object file
contains the data block that Binder compares with the compiler definition.
E Block does not exist in file: block-name
E Part of data block being dumped is not initialized
E Block is not on the include list
W Block length/address mode error on
data-block-name
Additional text is one of the following:
Blocks compared are from filename
and filename
Blocks compared are from filename
and the compiler