Impacts of changes made in AIP Core 8.3.5 on Quality Model results post upgrade

All technos

Avoid artifacts having recursive calls - 7388

A bug has been discovered which is causing the Quality Rule "Avoid artifacts having recursive calls - 7388" to be falsely violated. This violation is the result of an incoherence in the analyzer where an ABAP method is identified (incorrectly) as calling itself. This bug has now been fixed and after an upgrade to AIP Core 8.3.5, results may differ for this Quality Rule - there will be a reduction in false positives.

Mainframe Cobol

SCRAIP-32406 - Rules "Avoid SQL queries that no index can support - 7902" and "Avoid SQL queries on XXL tables that no index can support - 7904" report violations

A bug has been discovered which has meant that the rules "Avoid SQL queries that no index can support - 7902" and "Avoid SQL queries on XXL tables that no index can support - 7904" are returning violations for the Mainframe Cobol technology. This technology should not be included in the scope for these rules. This bug has been fixed and after an upgrade to AIP Core 8.3.5 and the generation of a post-upgrade consistency snapshot on the same source code, results may be impacted: reduced number of violations increasing accuracy.

Other impacts of changes made in AIP Core 8.3.5

Analysis Units for .NET Core Projects

In previous releases of AIP Core, the discoverer for .NET ignored .NET projects of type .NET Core. They were discovered but not selected in the package in the CAST Delivery Manager Tool. In AIP Core ≥ 8.3.5, projects of type .NET Core are now automatically "selected" in the CAST Delivery Manager Tool. As a consequence, when a user performs the Set as Current Version action in the CAST Management Studio, the .NET Core projects are imported and corresponding Analysis Units are created. Therefore, measures such as Lines of Code or Commented Code Lines will increase in a snapshot. Similarly, new quality rule violations can be found in the source code that is now analyzed. The exact impact on analysis results depends on the version of the .NET Analyzer extension that is used for the analysis and the level of support for .NET Core that the extension provides. Please refer to the extension documentation.

If you do not want .NET Core projects to be analyzed and results modified (with regard to a previous snapshot), please unselect .NET Core Analysis Units in the CAST Management Studio, after performing the Set as Current Version option.

Mainframe Cobol

SCRAIP-31872 - Mainframe Analyzer creates incorrect links between paragraphs containing EXIT statements and the next SECTION in the file

A bug has been discovered which is causing the Mainframe Analyzer to create incorrect links between paragraphs containing EXIT statements and the next SECTION in the file. This bug has been fixed and after an upgrade to AIP Core 8.3.5 and the generation of a post-upgrade consistency snapshot on the same source code, results may be impacted: reduced number of links potentially affecting transaction values.

SCRAIP-32164 - Line of code values for Mainframe Cobol analyses is incorrect when nested Cobol Programs are involved

A bug has been discovered which is causing line of code values for Mainframe Cobol analyses to be incorrect when nested Cobol Programs are involved. Lines of code for nested Cobol Programs are being counted twice: once as Cobol Programs and once as nested Cobol Programs. This bug has been fixed and after an upgrade to AIP Core 8.3.5 and the generation of a post-upgrade consistency snapshot on the same source code, results may be impacted: line of code values will be reduced where nested Cobol Programs are involved, increasing accuracy.

SAP/ABAP

SAP-99 and SAP-100 - Unresolved objects "wd_this" and "wd_assist" are created

The ABAP expressions "wd_this" and "wd_assist" were previously not recognized and caused the creation of unresolved objects. This syntax is now supported and therefore, after an upgrade to AIP Core 8.3.5 and the generation of a post upgrade snapshot, results may differ: there may additional objects and links possibly leading to a change in transaction values.

SAP-101 - Unresolved object "ANY" are created

The ABAP expression "ANY" was previously not recognized and caused the creation of unresolved objects. This syntax is now supported and therefore, after an upgrade to AIP Core 8.3.5 and the generation of a post upgrade snapshot, results may differ: there may additional objects and links possibly leading to a change in transaction values.