System Generation and Installation › Generation in the HE Environment › Specify Member Names › Dynamic Linking Parameters

Dynamic Linking Parameters

Use the Specify Member Names panel to specify how to dynamically link a particular procedure step, action block, or screen.

• Use DEF to default to the corresponding Dynamically Link value that is specified in the target environment parameters.
• Use YES to designate the module as one to be invoked using a dynamic program call. Programs invoked using a dynamic program call are considered to be dynamically linked at runtime. During load module installation, the components that have their associated dynamically link packaging property set, or derived, to Yes are built so they reside in their own separately loadable executables. These application routines reside in DLLs.
• Use NO to designate the module as one to statically link in the load module in which it is defined.
• Use CMP to designate the module as marked for Compatibility. A module marked for Compatibility is dynamically called at runtime and resides in a non-DLL module. Compatibility modules use specific CA Gen runtime to enable DLLs to issue a dynamic program call to non-DLL load modules. This requires regenerating and reinstalling the module issuing the dynamic program call. CA Gen allows modules that are marked for Compatibility to be rebuilt to use CA Gen runtime DLLs. This requires that the modules marked for Compatibility be reinstalled and, if necessary, regenerated.
• To maintain compatibility with previous Gen releases that only supported static batch procedure steps, CA Gen generates and installs Batch procedures that are set to DEF as static modules, regardless of the default dynamic link setting for the business system
• RI triggers and action blocks, including EABs, statically called by modules that are marked for Compatibility must be built using the NODLL compiler option. When these RI triggers and action blocks are also used in Gen applications that are built as DLLs, they must be compiled using the DLL option.
• Selecting the option Process modules that are marked for Compatibility causes the RI triggers and the statically called action blocks to be generated and precompiled once but compiled twice – once as NODLL and again as DLL.
• Separate the libraries are provided in the target environment to hold the separate NCAL modules resulting from the two compile steps.

Since the CMP option is not supported for a z/OS Library load module, do not use CMP for the modules that are listed under a z/OS Library. Doing so cause runtime errors that is reported by consistency check.