Binder Manual (G06.24+, H06.03+)

Using Binder
Binder Manual—528613-003
2-6
Binding Rules
The ADD * command causes all the code and data blocks from an object file to be
included in the target file. Therefore, if OBJFILEX contains PROC A, PROC B, and
PROC D, and OBJFILEY contains PROC C, PROC E, and PROC F, then TRGFILEZ
contains all six procedures.
If more than one object file includes the same code block name or data block name,
Binder retains the first one it encounters.
Binding Rules
The rules that govern binding depend on the run-time environment. Before the D-series
RVUs, C, COBOL85, FORTRAN, Pascal, and TAL each had its own run-time
environment. These language-specific run-time environments were different from one
another and often incompatible. With the D-series RVUs, the Common Run-Time
Environment (CRE) provides a shared run-time facility for C, COBOL85, Pascal,
FORTRAN, and TAL. D-series versions of the C and Pascal compilers always generate
programs that run in the CRE
1
. D-series versions of the COBOL85, FORTRAN, and
TAL compilers generate programs that can run in either a language-specific run-time
environment or the CRE, depending on the setting of the ENV directive.
Binder categorizes the ENV directive parameters into three groups: OLD, NEUTRAL,
and COMMON. For the most part, these groups match the various ENV parameters
provided by the language compilers.
•
OLD generates code that runs only in a language-specific run-time environment.
•
COMMON generates code that runs only in the CRE.
•
NEUTRAL generates code that runs in either a language-specific run-time
environment or the CRE.
1
The C and Pascal compilers generate code that runs in either a language-specific run-time
environment or the CRE if you specify the ENV LIBSPACE or ENV EMBEDDED directives.
These C and Pascal routines cannot perform I/O or access the heap, and therefore are not
useful in most situations.