External Action Blocks › Create External Action Blocks in HE › Modifying the External Action Block Stub › Dynamically Link Options

Dynamically Link Options

Use the Target Environment panel to set the dynamically link options or use the Specify Member Names panel to override the options for a specific module.

The Dynamically Link property for individual EABs can be set to DEF, YES, NO, or CMP. DEF is the default.

DEF

For a business system, a default value for the Dynamically Link property can be established for action blocks. The action block Dynamic Link Property can be YES (enabled), NO (disabled), or CMP (Compatibility). If enabled, the resulting Dynamically Link property for an individual EAB that is set to Default is interpreted as having been explicitly set to Yes. If disabled, the resulting Dynamically Link property for an individual EAB that is set to Default is interpreted as having been explicitly set to No. If Compatibility, the resulting Dynamically Link property for an individual EAB that is set to Default is interpreted as having been explicitly set to Compatibility.

YES

Indicates that the associated EAB is invoked using a dynamic program call. The EAB must be built in its own fully resolved executable and must reside in a DLL.

NO

Indicates that the associated EAB is not to be the target of a dynamic program call, and as such isis statically linked into its identified owning load module.

CMP - Compatibility

Indicates to invoke the associated EAB using a dynamic program call. The EAB is expected to be a z/OS non-DLL load module that follows LE linkage conventions. To regenerate the EAB stub, select the generation option Process modules that are marked for Compatibility.

If regenerated, the EAB must then be rebuilt as a z/OS non-DLL load module. After rebuilding, put the NCAL EAB in a library in the External Compatibility Libraries panel. Modules containing calls to EABs that are marked for Compatibility require that they be generated so they can use runtime code to perform the DLL to non-DLL load module dynamic program call.

If the EAB marked for Compatibility or its callers contain SQL code, the DB2 BIND is redone. DBRMs for the generated caller module are automatically produced and used. However, DBRMs belonging to the EAB marked for Compatibility is resolved and made available to the BIND step.