This option applies to MVS applications, which have components that either explicitly or by default are configured with their Dynamically Link packaging property set to Compatibility. Compatibility is intended to be used by applications that make use of one or more dynamically called modules that for some reason must reside in a non-DLL module.
Typically the components marked for Compatibility include:
Use the Process modules marked for Compatibility option to generate and install modules marked for Compatibility. If the option is not set, the processing of components marked for Compatibility will be bypassed. Selecting the Process modules marked for Compatibility option causes all Action Blocks statically called by a module marked for Compatibility to be compiled twice-once using the compiler option NODLL and again using the compiler option DLL.
The result of the NODLL compile is linked into the Compatibility module. The result of the DLL compile is provided so that it can be linked into any DLL applications that statically call these action blocks. If the action blocks are External Action Blocks, they must be compiled using the appropriate compiler options and made available to be included in the install of the final load module.
Selecting the Process modules marked for Compatibility option when generating and installing RI triggers causes the RI trigger modules to be generated and precompiled once but compiled twice in a similar way to Action Blocks.
Separate libraries are provided in the target environment to hold the separate NCAL modules resulting from the two compile steps.
|
Copyright © 2013 CA.
All rights reserved.
|
|