Changes in results post upgrade - 8.3.22

Created by James Hurrell on Feb 25, 2021

Summary: this page lists:

  • Impacts of changes made to AIP Core8.3.22 on Quality Model results post upgrade

  • Other impacts of changes made in AIP Core8.3.22

All changes in results related to extensions are now listed in the extension documentation and will not appear in this page.

Impacts of changes made in AIP Core8.3.22 on Quality Model results post upgrade

JEE/.NET

High Efferent and High Afferent rules

A fix has been applied to the following rules:

This fix resolves an issue where an inconsistent number of violations were being reported for these rules. The fix changes the range of objects taken into account for these rules for both technologies:

  • Java Packages and .NET Namespaces that are considered external to the Application (e.g. Java libraries such as rt.jar or .NET assemblies) are now taken into account where previously they were not
  • Java Enum and .NET Enumeration objects are now taken into account where previously they were not.

As a result of this change, results may be impacted for these rules if a consistency snapshot is generated: the number of outgoing and incoming dependencies for packages and namespaces may now increase due to the change in the range of objects and therefore this may trigger a violation of the rules. In other words, more violations may be present than previously.

Mainframe

Never truncate data in MOVE statements - 7688

A fix has been applied to the rule Never truncate data in MOVE statements - 7688 to resolve an issue where false violations were being reported where only one variable of OCCURS ... DEPENDING ON exists. As a result of this fix, results may be impacted for the rule if a consistency snapshot is generated - less false violations will be reported, improving the accuracy of this rule.

Avoid GOTO jumps out of PERFORM range - 7274

A fix has been applied to the rule Avoid GOTO jumps out of PERFORM range - 7274 to improve the time taken to calculate this rule: where source is deemed to be semantically incorrect (which is the cause of the slow calculation time for this rule), the calculation of this rule will be skipped. As a result of this fix, results may be impacted for the rule if a consistency snapshot is generated - less false violations will be reported if the analysis engine deems the source code to be semantically incorrect.

Other impacts of changes made in AIP Core8.3.22

Mainframe

JCL Symbol resolution

JCL symbolic parameter values are now correctly propagated from JCL to procedures in the call chain. As a result of this, results may be impacted if a consistency snapshot is generated - some JCL dataset objects will be renamed.

CAST Engineering Dashboard

A fix has been applied to resolve an issue where the number of violations for a given rule in the Risk Investigation view in the Engineering Dashboard differ in the left hand and right panels. This issues is a display issue, and results in themselves are not impacts by the fix.