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

Binder Input and Output
Binder Manual—528613-003
5-11
How Binder Builds the Target File
Note that the Inspect symbolic debugger also provides an interactive method for saving
the environment of a process as well as examining save files. See the descriptions of
the SAVE and PR commands in the Inspect Manual.
How Binder Builds the Target File
When the BUILD command executes, Binder creates the target file according to the
code block, data block, entry point, and RTDU names currently on the include lists.
Binder performs the following steps in creating the target file:
1. It tries to satisfy entry point, data block, and RTDU references in the unresolved
and undefined reference lists.
2. It defines entry points that cannot be resolved as external references for the object
file.
3. It allocates any uninitialized common block in an area preset to zero.
4. It copies blocks named in the include lists to the target file.
Binder allocates code blocks contiguously in the order in which the code block names
appear in the include code block list. The RESIDENT attribute overrides the include list
order.
If you have set the COMPACT parameter of the SELECT command to ON (the
default), Binder checks each succeeding code block to determine whether the block fits
in a gap between the previous code block and the 32K boundary. If Binder finds such a
block, Binder allocates the block in that gap. Use of the SELECT COMPACT ON
command can result in nonresident code blocks preceding resident code blocks.
The CHECK parameter of the SELECT command can also affect the construction of
the target file. This parameter selects the different types of error checking that Binder
provides during the binding operation. The available options are as follows:
SYSTYPE Specifies whether the target execution environment for
the object file is Guardian environments or OSS
environment. The default is Guardian.
TARGET Specifies the processor that the target file can run on.
TARGET can be TNS, TNS/R, ANY, or unspecified. The
default is unspecified.
USERLIBRARY Specifies whether Binder builds a target file with a
maximum of 16 or 32 code segments. If you specify the
latter, the process creation system procedure call
creates a process with the first 16 code segments in user
code space and the remaining segments in the user
library space. The default value, OFF, specifies a
maximum of 16 code segments.
Table 5-2. Target File Attributes (page 3 of 3)
Attribute Description