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

Binder Messages
Binder Manual—528613-004
8-13
Error Messages and Warnings
61
SELECT CHECK PARAMETER is STRICT (default), and the consistency check failed.
The type of the indicated parameter differs from that required by the named entry point.
Binder also issues this message if calls to the same entry point from separately
compiled code blocks specify incompatible types.
Binder goes on to say whether the mismatch was between two external declarations of
a procedure or between an external declaration and the actual procedure declaration.
Binder detects when at least one parameter is of type INT, INT(32), or STRING and
informs you.
If only one parameter is INT, INT(32), or STRING, Binder designates the parameter
that is not one of those types as “other.” If neither parameter is INT, INT(32), or
STRING, Binder outputs more detailed information on the mismatch, including one or
more of the following: parameter storage type, parameter length in bits, number of
units, and number of digits to the right of the decimal point.
62
This error can occur with FORTRAN or TAL input files.
For FORTRAN, this error means that too many variables in FORTRAN COMMON are
referenced. Recompile using the ?EXTENDCOMMON compiler directive.
For TAL, this error means that too many global variables are defined. Modify your
global data space.
63
This error occurs on TAL input files.
The RELOCATE directive was used and relocation might have occurred. The
#GLOBAL block is not at offset zero. The compiler and command-driven Binder issue
warnings.
W Parameter type mismatch on entry-point-name
parameter n
E Primary global area overflow
W Procedure references absolute global data which
may be relocated: code-block-name