When an External Action Block has its associated Dynamically Linked Packaging property set to Yes, migrating to CA Gen 8.5 requires recompiling the EAB and reinstalling it as a DLL. If the EAB dynamically calls other user programs, those user programs must also be built as DLLs.
When an External Action Block has its associated Dynamically Linked Packaging property set to Compatibility, the option Process modules that are marked for Compatibility determine if the EAB must be rebuilt as a z/OS non-DLL load module or remain as built by the releases of CA Gen earlier to release 7. If the EAB dynamically calls other user programs, those user programs must also be non-DLLs.
How an External Action Block that has its associated Dynamically Linked Packaging property set to No, so it is statically linked into the calling application, must be compiled depends on the type of application that calls it. When the calling application is marked for Compatibility the EAB must be built using the NODLL compiler option and must be placed in a library in the Compatibility EAB load libraries panel. When the calling application is not marked for Compatibility the EAB must be built using the DLL compiler option and must be placed in a library in the EAB Load libraries panel. When called by both application types, two copies of the EAB must be built and each placed in the appropriate load library.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|