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

Using Binder
Binder Manual—528613-003
2-4
Specifying the Target File Order
You must supply the disk file name of the correct object file before Binder accepts the
name of a code or data block for an include list. The file Binder uses as the default for
block retrieval is the current file. Either a block must be in the current file or you must
specify the file when you add the block. You can change the current file designation as
often as you want by using the FILE command.
Specifying the Target File Order
Binder assumes the order you specify is the order you prefer for the code blocks in the
target file. (You cannot establish the ordering of data blocks in the target file
beforehand.)
Binder builds lists of target file specifications from your commands and from input
object files. You need at least one include list for the binding process; the other lists are
optional.
Table 2-1. Target File Specifications built by Binder (page 1 of 2)
Name of List Number of Lists Allowed Description
Include Lists 4 These lists reflect the order in which
Binder encounters code blocks, data
blocks, entry point names, or run-time
data units (RTDUs) and the order in
which Binder builds the target file. There
is one include list for code blocks, one for
data blocks, one for entry point names,
and one for RTDUs.
Omit List 1 This list is for external references to entry
points that Binder is not to resolve,
regardless of the names included.
Refer List 1 This list holds pairs of entry point names;
the first name satisfies references to the
second. For example, an entry point to a
code stub (that is, a block skeleton) can
satisfy references to code that is not
ready.
Modify List 1 This list contains an entry for every code
or data block patch.