Intelligent Regeneration › Processing Logic › z/OS Compatibility Option Considerations

z/OS Compatibility Option Considerations

When dynamically link default options are modified at the Business System level, Intelligent Regeneration processes individual modules using Default value for the dynamically link option if Ignore Target Environment Parameter Changes option is set to No on Regeneration Options panel. If this option is set to Yes, Intelligent Regeneration ignores the modifications that are made at the Business System level.

When the dynamically link option is changed to CMP(compatibility), for an action block, Intelligent Regeneration marks the calling module as requiring regeneration because the call statement is different in the caller module. IIntelligent Regeneration will also list compatibility action blocks as required to be regenerated when their dynamic flag is changed to CMP, although they only require to be relinked. This is because change capture or Intelligent Regeneration does not know what was changed. This behavior is the same for action blocks with dynamically link option set to DEF (Default), when the Business System defaults change to CMP and Ignore Target Environment Parameter Changes option is set to No.

Intelligent Regeneration does not list screen modules as requiring regeneration when their dynamic flag is set to CMP. Instead it lists their associated action blocks as requiring regeneration because when a screen's dynamic flag is modified, change capture flags the action block as changed and not the screen.

After identifying the components, Intelligent Regeneration provides generation and installation options panels similar to those in Host Construction. These Intelligent Regeneration panels and dialogs include a Process modules marked for Compatibility Yes/No option to indicate that modules marked for Compatibility should or should not be processed, similar to Host Construction.

• When this option is set to No, Intelligent Regeneration behaves the same as in the AllFusion Gen 7.6 release without the Compatibility Priority Enhancement. CA Gen bypasses the generation, installation, remote installation processing, or both of modules that are marked for Compatibility. When Intelligent Regeneration runs again, the Compatibility modules are listed as requiring regeneration or reinstallation even though their processing was specifically bypassed because Intelligent Regeneration uses the generation or installation timestamp in decision making.
• When this option is set to Yes, modules marked for Compatibility are processed, that is generation, installation, inclusion for remote installation, or both occurs, only if they are included within the scope of those modules that are selected for processing. When Intelligent Regeneration runs again, Compatibility modules are not listed as requiring regeneration, or reinstallation if they were previously generated or installed, and the module was not modified since the last Intelligent Regeneration run, such as modifying the action diagram on the Toolset.

Selecting the Process modules marked for Compatibility option causes the RI Trigger modules and all Action Blocks statically called by the module marked for Compatibility to compile twice, once using the NODLL compiler option and again using the DLL compiler option.

The result of the NODLL compile is linked into the Compatibility module. The result of the DLL compile can be linked into DLL applications that statically call these components.

Intelligent Regeneration identifies the Compatibility modules if Process modules marked for Compatibility option is set to Yes.