This option applies to MVS applications with components configured with the dynamically link packaging property set to Compatibility. Compatibility is intended for use by applications that dynamically call modules that must reside in a non-DLL module.
Important! All modules within an application are subject to the support policy of the CA Gen release in which they are produced. Using the Compatibility feature without selecting the Process modules marked for Compatibility option does not change the support policy or support timeframe that is associated with those modules that are marked for Compatibility. Therefore, modules that are marked for Compatibility and their components are supported at the release level at which they are built.
Components that are marked for Compatibility include:
Use the Process modules marked for Compatibility option to generate or install modules that are marked for Compatibility. Failing to set the option bypasses processing of components that are marked for Compatibility.
Selecting the Process modules marked for Compatibility option generates and precompiles the RI Trigger modules and all Action Blocks statically named by the module marked for Compatibility, and compiles them twice, once using the NODLL compiler option and again using the DLL compiler option.
The result of the NODLL compile is linked into the module marked for Compatibility. The result of the DLL compile is provided so that it can link into any DLL applications that statically call these triggers or action blocks. If the action blocks are External Action Blocks, they must be compiled using the appropriate compiler options and is available to include in the final load module install.
Separate the libraries in the target environment hold the separate NCAL modules resulting from the two compile steps.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|