Rational Developer for System z
PL/I for Windows, Version 7.6, Programming Guide

Producing a dynamic link library

A dynamic link library (.DLL) file contains executable code for common functions, just as a library (.LIB) file does. When you link with a DLL (using an import library), the code in the DLL is not copied into the executable file. Instead, only the import definitions for DLL functions are copied, resulting in a smaller executable. At run time, the dynamic link library is loaded into memory, along with the .EXE file.

To produce a DLL as output, compile at least one object file with the DLLINIT compiler option, and link it with the /DLL linker option. You must include an export definition (.EXP) file that specifies which functions are to be included in the DLL.

You can find more information in Building dynamic link libraries.

To reduce the size of the DLL and improve its performance, use the following options:

For DLLs, setting a /BASE value can save load time when the given load address is available. If the load address is not available, the /BASE value is ignored, and there is no load time benefit.

Once you have produced the DLL, you can produce an executable that links to the DLL.

The linker determines which functions your object files need during the linking process. Use the ILIB utility to create an import library, and then use the .LIB file as input to the linker.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)