If DYNAM(DLL) is enabled and the module contains exported symbols,
the binder will build the control structures enabling the output module
to be used as a DLL. The functions or variables exported by the DLL
can be imported by DLL applications. If DYNAM(DLL) is enabled, and
the module contains symbols eligible for dynamic resolution, and these
symbols match symbols on IMPORT control statements, then the binder
will build the control structures enabling the output module to execute
as a DLL application. A DLL application can use functions or variables
exported by DLLs.
You can specify the DYNAM option in the PARM field as follows:
Note: - When DYNAM (DLL) is specified, a side file of IMPORT control statements
might be generated by the binder.
- If you are using the batch interface of the binder, the IMPORT
control statements are saved in the data set specified in the SYSDEFSD
ddname in your JCL. See SYSDEFSD DD statement. If you are
using the binder API, the side file is saved in the data set represented
by the SIDEFILE specification of the files parameter
of the STARTDialog API. For more information, see z/OS MVS Program Management: Advanced Facilities.
- A module linked with the DYNAM(DLL) option will be saved in a
PO3 format program object unless you specify a higher COMPAT option
or other features that force saving in an alternate format program
object.
- The DYNAM option disables the RES option.