When migrating from releases earlier than AllFusion Gen 7 to CA Gen Release 8.5, evaluate the application components that can become DLLs and the application components that must remain as non-DLL load modules.
Note: It is possible that feature enhancements offered in future releases of CA Gen require that routines reside in a DLL to use those features.
Some of the application components that can become DLLs are regenerated and all the components are recompiled, re-linked, and re-installed regardless of the application type, (block mode or servers), or the type of linkage, (static or dynamic program call), used between application components.
The following list describes the components that must be regenerated or reinstalled-for each application type. Reinstallation implies recompile, re-link and if applicable bind.
No components require regeneration. All components require re-installation.
Batch Manager requires regeneration. All components require re-installation.
Dialog Manager requires regeneration. All components require re-installation.
Dialog Manager and Map require regeneration. All components require re-installation.
Dialog Manager requires regeneration. All components require re-installation.
Dialog Manager and Map require regeneration. All components require re-installation.
Dialog Manager requires regeneration. All components require re-installation.
Dialog Manager and Map require regeneration. All components require re-installation.
Server Manager requires regeneration. All components require re-installation.
Server Manager requires regeneration. All components require re-installation.
Components that remain as non-DLL load modules must use the z/OS Dynamic Program Call Compatibility feature.
This feature allows a phased migration of applications that are built by releases of AllFusion Gen before Release 7, that use dynamically called procedure steps, screens, or action blocks (including EABs). The Compatibility setting causes the caller of a module marked for compatibility to always be regenerated and reinstalled, to include a call to the runtime routine that handles the call to the non-DLL load module. The option Process modules that are marked for Compatibility determine which components are rebuilt as CA Gen Release 8.5 non-DLL load modules. The option Process modules that are marked for Compatibility can be selected to regenerate and reinstall components or only to reinstall them. The reinstall is required to enable the non-DLL load modules to use the CA Gen Release 8.5 DLL runtimes.
RI triggers and action blocks that are statically called by modules that are marked for Compatibility must be built using the NODLL compiler option. If these RI triggers and action blocks are also used in CA Gen applications built as DLLs, they must be compiled using the DLL option.
Selecting the Process modules marked for Compatibility option causes the RI triggers and action blocks that are statically called by modules that are marked for Compatibility to be generated and precompiled once, but compiled twice. Separate the libraries are provided in the target environment to hold the separate NCAL modules resulting from the two compile steps.
Applications that run under TSOAE and contain modules that are marked for Compatibility cannot dynamically call modules that are built with a release earlier than AllFusion Gen 7.6.
Enhanced Map Block Mode applications containing screens that are marked for Compatibility cannot dynamically call screen managers that are built with a release before AllFusion Gen 7.6.
The option Force compile of all components can be used to recompile and relink all application components, except for EABs or user exits which must be done separately.
Important! Ensure that runtimes from previous releases are not inadvertently picked up from the SYSLIB concatenation through an auto-call. The CA Gen Release 8.5 load library contains all the required runtimes. Load libraries from previous releases must not be included in the SYSLIB concatenation.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|