Migrating from the prelinker to Binder

Users must ensure that their JCL and the cataloged procedures they are invoking are changed to eliminate the prelinker step.

Note: The c89 command in z/OS UNIX will bypass the prelinker and compilers such as the IBM® C/C++ compiler may provide new cataloged procedures that will use the binder for prelinker functions.

The following considerations apply if you are converting JCL yourself. It is assumed that you have already performed any necessary conversion from the linkage editor to the binder.

The members of the SYSLIB concatenation used in the prelink step should be concatenated before the SYSLIB members used in the bind step.
Specify CASE(MIXED) as a binder option to preserve case sensitivity.
The contents of the prelinker SYSIN can be used as the binder SYSLIN or concatenated with it, or explicitly included by a binder INCLUDE control statement.
SYSLMOD must be allocated to a PDSE or an z/OS file.
If SYSDEFSD was being used for the prelinker step, it should be added to the bind step.
If a DLL-enabled module is produced, DYNAM(DLL) must be specified. The prelinker produced a DLL-enabled module if the input XOBJ was DLL-enabled. The binder requires an explicit directive.
If the prelinker UPCASE option was being used, it can be specified as a binder option. However it might not be necessary since the binder provides better support for long and mixed case names.
Prelinker control statements, including RENAME and IMPORT, can be moved from the prelink step to the bind step.