I have a static link of 6.5 modules residing in a 7.6 application. Can I resolve the CA GEN 6.5 runtime calls?
Release: KGNCRK05500-7.6-Gen-CLS Runtime Kit-for Unisys
Static link of CA GEN 6.5 modules into a CA GEN 7.6 application results in unresolved externals. Static linking of 6.5 modules into 7.6 applications is not supported. All components not "compatible" need to be recompiled when migrating from 6.5 to 7.x.
In CA GEN 7.x and upwards, all modules are compiled with the DLL option. The CA GEN 6.5 modules are compiled with the NODLL option. All modules in a "unit" (by "unit" I mean everything that is linked together and is it's own member in the load lib) need to be compiled with the same option, either DLL or NODLL. If this is not the case, you might get the link edit to work but you may run into other problems at runtime. It is not safe to mix DLL and NODLL in the same "unit". You will get unpredictable results or even abends.
The compatibility option offers a way of letting dynamic action blocks remain as NODLL. They reside in their own "unit" and everything in it needs to be NODLL. We then use the TIRLGLOD mechanism to resolve the call from a DLL "unit" to a NODLL "unit".