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

User Libraries
Binder Manual—528613-004
6-2
Object File Format
library code space for a total of 64 segments. A segment can contain as many as 64K
words of code. For instructions about using the USERLIBRARY option to increase the
size of a program’s code space from 16 to 32 segments (for TNS systems) and from
32 to 64 segments (for TNS/R systems), see SET Command on page 3-57.
Object File Format
Because the operating system binds program files and library procedures at execution
time, there are no restrictions on object-file format. A program file and its library file can
exist in any combination of new Binder and old system formats.
Preventing Binder Resolution of Library Calls
If you plan to use a user library (for example, to avoid code-space overflow), make
sure Binder does not insert library procedures into the object file before run time. This
can be accomplished at compile time or during a command-driven BIND session.
Compilation-Time Binding
At compilation time, Binder tries to resolve external references if the compiler SEARCH
directive or pragma specifies a list of object files for this purpose. The exception to this
is COBOL85’s use of the file C8LIB. For more information, see the COBOL85
Reference Manual.
When a search list is present, the Binder tries to resolve all unresolved external
references. If compilation-time binding places a user-library procedure in the program
file, you can delete that procedure from the program file in an independent Binder
session.
Command-Driven Binding
During a Binder session, you can specify names of individual entry points that Binder
should not include in an object file. First build a user-library file of procedures copied
from existing program files; then, build more compact program files by omitting the
library procedures.
To specify the external references that Binder should not resolve, use these commands
as appropriate:
•
The SELECT OMIT command to entry points of user library procedures.
This prevents binding of these procedures in the program file.
•
The BUILD command with the SATISFY OFF parameter option.
This, however, prevents any attempt at resolution after the target file contents have
been specified by other commands.
•
The DELETE command to remove user-library procedures that were already
bound in the program file.