Summary: this page lists:
- Impacts of changes made to AIP Core 8.3.8 on Quality Model results post upgrade
Other impacts of changes made in AIP Core 8.3.8
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 Core 8.3.8 on Quality Model results post upgrade
Multi-techno
SCRAIP-32977 - Avoid Artifacts with high Commented-out Code Lines/Code Lines ratio - 7126
A bug has been discovered which is causing erroneous results for the rule "Avoid Artifacts with high Commented-out Code Lines/Code Lines ratio - 7126": when there is no change in source code or configuration between successive analyses, the violation status for random objects will change (i.e. some objects that previously were not listed as violating the rule in the first analysis are now violating the rule in the second analysis). This bug has been fixed by altering the rule's algorithm, therefore, after an upgrade to AIP Core 8.3.8 and the generation of a post-upgrade consistency snapshot on the same source code, results will differ for this rule.
SCRAIP-33762 - Avoid artifacts having recursive calls - 7388
A bug has been discovered which is causing erroneous results for the rule "Avoid artifacts having recursive calls - 7388": violations are being raised on objects that do not contain recursive calls. This bug has been fixed, therefore, after an upgrade to AIP Core 8.3.8 and the generation of a post-upgrade consistency snapshot on the same source code, results may differ for this rule.
Other impacts of changes made in AIP Core 8.3.8
SAP ABAP
SAP-125 - Incorrect links creation and links not discovered
A bug has been discovered which is causing erroneous analysis results: incorrect and missing links between objects and as a result "undefined objects" are created. This bug has been fixed, therefore, after an upgrade to AIP Core 8.3.8 and the generation of a post-upgrade consistency snapshot on the same source code, results may differ.
Mainframe Cobol
SCRAIP-32924 - Missing links between DB segment and DB segment parent objects
A bug has been discovered which is causing erroneous analysis results: there are missing "BelongsTo" links between DB segments and DB segment parent objects. This bug has been fixed, therefore, after an upgrade to AIP Core 8.3.8 and the generation of a post-upgrade consistency snapshot on the same source code, results may differ.
SCRAIP-33864 - Missing link between COBOL Program and CopyBook
A bug has been discovered where the analyzer expects a dot (.) to denote the end of an EXEL SQL block. This means that where this period is not used, the analyzer cannot identify the end of the block and therefore links between the COBOL program and COBOL copybooks are missed. In the following, there is no dot (.) after INCLUDE DLI05901, END-EXEC, and because of that the analyzer will not create links to DLI00001.
163600***************************************************************** 00 163700**** STUFF 00 163800 EXEC SQL 00 163900 INCLUDE DLI05901 00 164000 END-EXEC 00 164200 00 164300**** OTHER STUFF 00 164400 EXEC SQL 00 164500 INCLUDE DLI00001 00 164600 END-EXEC. 00 164700/ 00 164800**** SOME OTHER STUFF 00 164900 EXEC SQL 00 165000 INCLUDE DLI7003O 00 165100 END-EXEC. 00 165300 00 165400 DS00800-STAFF-SQL. 00 165500***************************************************************** 00
This bug is now fixed and the situation described above is now handled. Therefore, after an upgrade to AIP Core 8.3.8 and the generation of a post-upgrade consistency snapshot on the same source code, results may differ: possible increased number of links, violations and Function Point values providing improved accuracy.
.NET
SCRAIP-33859 - DMT DotNet Discovery is not replacing DLL reference with project reference when project is available in source code
A bug has been discovered which is causing a missing project alert to be raised by the CAST Delivery Manager Tool even though the project exists. This is due the fact that the CAST Delivery Manager Tool uses the DLL's full path rather than just the DLL's file name to identify the DLL, causing the corresponding project to not be found. This bug has now been fixed and missing project alerts for this situation will no longer be raised.