On this page:
Target audience:
CAST AI Administrator
Summary: this page lists:
- Impacts of changes made to CAST AIP 8.3.5 on Quality Model results post upgrade
Other impacts of changes made in CAST AIP 8.3.5
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 CAST AIP 8.3.5 on Quality Model results post upgrade
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 CAST AIP 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 CAST AIP 8.3.5
.NET - discoverers modified to take into account .NET Core/.NET Standard
The existing .NET discoverers for the Changes in results post upgrade - 8.3.5 are embedded in the CAST Delivery Manager Tool. These discoverers have been modified in this release of CAST AIP to take into account .NET Core 2.0 / .NET Standard 2.0 projects in preparation for .NET Core 2.0 /.NET Standard 2.0 analysis support in the forthcoming version 1.1.0 of the Changes in results post upgrade - 8.3.5. Therefore after upgrade to CAST AIP 8.3.5 and the generation of a post-upgrade snapshot, you may find that new .NET projects (corresponding to .NET Core 2.0 / .NET Standard 2.0 source code if that existed in the existing CAST Delivery Manager Tool packages) are selected and transformed into Analysis Units in the CAST Management Studio. Subsequent analysis of these Analysis Units during the post-upgrade snapshot will be successful, however, note the following:
- There will be an increase in objects/links related to .NET Core 2.0 / .NET Standard 2.0
- The analysis will, however, be incomplete:
- There will be no links to the .NET Core 2.0 / .NET Standard 2.0 framework
- No client server/links links
- Frameworks are not handled
- Some Rule may produce false negatives
See also Changes in results post upgrade - 8.3.5 for information about what the CAST Delivery Manager Tool considers a .NET Core 2.0 / .NET Standard 2.0 project.
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 CAST AIP 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 CAST AIP 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 CAST AIP 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 CAST AIP 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.