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

Binder Input and Output
Binder Manual—528613-003
5-3
How Binder Uses the Input Control Lists
How Binder Uses the Input Control Lists
The following subsections describe the input control lists and how and when Binder
adds and removes blocks and entry points from the lists.
Include Lists
The include lists are ordered lists of code blocks, data blocks, entry points, and RTDUs
to include in the target file. The ADD or REPLACE commands add the names of code
blocks, data blocks, entry points, and RTDUs to the applicable include list in the order
specified. Binder adds names from subsequent ADD commands to the end of the list.
REPLACE puts the replaced blocks in the same place on the list.
ADD and REPLACE commands can refer to entry points explicitly by name or implicitly
as part of a range of entry point names. Inserting a range of entry points specifies that
entry points in the file (in physical order) from the beginning to the end of the range are
to be added to the include list. All primary entry point names within the range are
added to both the include code block list and the include entry point list; secondary
entry point names are only added to the include entry point list. Names of own data
blocks for the code blocks are added to the include data block list.
If a code block added to the include code block list contains a reference to an entry
point, data block, or RTDU that is not in the respective include list, Binder adds the
name to the unresolved reference list. Binder tries to resolve the reference when you
execute a SATISFY or BUILD command. (You can prevent automatic resolution of
entry points and RTDUs by using the SELECT SATISFY OFF command.)
Include Code Block List.
Binder adds a code block name to the include code block list when one of the following
happens:
•
An ADD or REPLACE command refers to the code block (primary entry point)
name explicitly or implicitly as part of a range of entry points.
•
An ADD or REPLACE command refers to the total contents of a disk file containing
the code block.
•
Binder executes a SATISFY or BUILD command and the following are true:
°
An entry point, referenced by an included code block, is in the unresolved
reference list.
°
The entry point name is not in the omit list.
°
The code block containing the entry point that can satisfy the reference is in a
disk file in the search list.
The order of code block names in the include code block list generally determines the
order in which code blocks are allocated during the output phase. Binder might change
the order of code block names in three cases: