Notes® on the prelinking process

You cannot use the prelinker if you are using the XPLINK, GOFF, or LP64 compiler options. IBM® recommends using the binder instead of the prelinker whenever possible.

The prelinker was designed to process long names and support constructed reentrancy in earlier versions of the C compiler on the IBM MVS™ and OS/390® operating systems. The Language Environment® prelinker provides output that is compatible with the linkage editor, which is shipped with the binder.

The binder is designed to include the functions of the prelinker, the linkage editor, the loader, and a number of APIs to manipulate the program object. Thus, the binder is a superset of the linkage editor. Its functionality provides a high level of compatibility with the prelinker and linkage editor, but provides additional functionality in some areas. Generally, the terms binding and linking are interchangeable. In particular, the binder supports:

Inputs from the object module
XOBJ, GOFF, load module and program object
Auto call resolutions from z/OS® UNIX archives and C370LIB object directories
Long external names
All prelinker control statements

Notes:

You need to use the binder for XPLINK objects.
As of z/OS V1R7, the Hierarchical File System (HFS) functionality has been stabilized and z/OS File System (zFS) is the strategic file system for z/OS UNIX System Services. The term z/OS UNIX file system includes both HFS and zFS.

For more information about the compatibility between the binder, and the linker and prelinker, see z/OS MVS Program Management: User's Guide and Reference.

Updates to the prelinking, linkage-editing, and loading functions that are performed by the binder are delivered through the binder. If you use the Language Environment prelinker and the linkage editor (supplied through the binder), you have to apply the latest maintenance for the Language Environment element as well as the binder.