Input to the binder
- One or more object modules.
- Binder control statements (that you can generate using the PUNCH assembler statement).
- Previously linked program modules you want to combine into one load module.
- A sequential data set.
- A member of a partitioned data set.
- A member of a PDSE (if you are using the binder to link your program).
- Concatenated data sets of any combination of the above.
The primary input data set can contain object modules, binder control statements, and linked program modules.
You specify the primary input data set with the SYSLIN DD statement.
Secondary input to the binder can consist of object modules or program modules that are not part of the primary input data set, but are included explicitly or automatically in the program module using the automatic call library process.
An automatic call library contains modules that you can use as secondary input to the binder to resolve external symbols left undefined after all primary input has been processed.
- Libraries containing object modules, with or without binder control statements.
- Libraries containing linked program modules.
Secondary input for the binder is composed of either all object modules or all load modules, but it cannot contain both types. Secondary input for the binder can be any combination of object modules, load modules libraries, and program object libraries.
//SYSLIB DD DSNAME=ORDERLIB,DISP=SHR
// DD DSNAME=SALESLIB,DISP=SHR
In this case, both the partitioned data sets (library) named ORDERLIB and SALESLIB are available as the automatic call library. The LIBRARY control statement has the effect of concatenating any specified member names with the automatic call library.