Binding your DLL code

Use the DLL support in the DFSMS binder, rather than the linkage editor, for linking DLL applications. Note that binder-based DLLs must reside in PDSEs, rather than PDS data sets. If a DLL must reside in a PDS load library, the application must be prelinked with the Language Environment prelinker before standard linkage editing. See Prelinking an application for further details. When binding a DLL application using the DFSMS binder, the following binder externals are used:

The binder option CASE(MIXED) is required when binding DLLs that use mixed-case exported names.
The binder options RENT, DYNAM(DLL), and COMPAT(PM3) or COMPAT(CURRENT) are required.
When binding a DLL, a SYSDEFSD DD statement must be specified, indicating the data set where the binder should create a DLL definition side-deck. The DLL definition side-deck contains IMPORT control statements for each of the symbols exported by a DLL. If you are using z/OS UNIX, specify the following option for the bind step for c89 or the c++ command:
```
-W l,DLL
```
If the code in the DLL was compiled with the XPLINK compiler option, specify:
```
-W l,DLL,XPLINK
```
The binder SYSLIN input, the binding code that references DLL code, must include the DLL definition side-decks for the DLLs that are to be dynamically referenced from the module being bound. See z/OS MVS Program Management: User's Guide and Reference and z/OS MVS Program Management: Advanced Facilities for further details.