The program management binder

The binder provided with z/OS® combines the object modules, load modules, and program objects comprising an application. It produces a single z/OS output program object or load module that you can load for execution. The binder supports all C and C++ code, provided that you store the output program in a PDSE member or a z/OS UNIX file.

If you cannot use a PDSE member or z/OS UNIX file, and your program contains C++ code, or C code that is compiled with any of the RENT, LONGNAME, DLL or IPA compiler options, you must use the prelinker. C and C++ code compiled with the GOFF or XPLINK compiler options cannot be processed by the prelinker.

Using the binder without using the prelinker has the following advantages:

Faster rebinds when recompiling and rebinding a few of your source files
Rebinding at the single compile unit level of granularity (except when you use the IPA compile-time option)
Input of object modules, load modules, and program objects
Improved long name support:
- Long names do not get converted into prelinker generated names
- Long names appear in the binder maps, enabling full cross-referencing
- Variables do not disappear after prelink
- Fewer steps in the process of producing your executable program

The Language Environment® prelinker combines the object modules comprising a z/OS XL C/C++ application and produces a single object module. You can link-edit the object module into a load module (which is stored in a PDS), or bind it into a load module or a program object (which is stored in a PDS, PDSE, or z/OS UNIX file).