Summary: this page lists:
- Impacts of changes made to AIP Core 8.3.24 on Quality Model results post upgrade
Other impacts of changes made in AIP Core 8.3.24
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.24 on Quality Model results post upgrade
Mainframe
Support for VSAM commands in "SYSIN" clauses
Support has been introduced for VSAM commands in "SYSIN" clauses, for example:
- ALLOCATE
- ALTER
- DEFINE
- DELETE
- EXAMINE
- LISTALC
- LISTCAT
- LISTDS
- REPRO
- VERIFY
As a result, existing results may be impacted if a consistency snapshot is generated: the number of violations for some Mainframe rules may change (increase or decrease) and
New rules enabled
The following new rules have been enabled in AIP Core 8.3.24 - as a result after upgrade to AIP Core ≥ 8.3.24 and the generation of a consistency snapshot:
- a change in the number of violations for your Mainframe application may be visible (an increase or decrease is possible)
- a change in the number of Cobol related object properties for your Mainframe application may be visible
8468 | Program semantic should respect the logic of flow execution |
---|---|
8470 | Avoid using STRING without overflow check |
8476 | Avoid calling unsafe C library functions from COBOL |
8478 | Avoid Buffer Overruns when using ADD, SUBTRACT, MULTIPLY, DIVIDE & COMPUTE statement inside a loop |
8480 | Avoid using PREPARE STMT statement (Dynamic SQL) with STRING containing HOST variables |
File descriptor block must be defined with 0 record - 7366
The algorithms used to calculate the rule File descriptor block must be defined with 0 record - 7366 have been improved to reduce the number of false positive violations returned by this rule. As a result of this fix, existing results may be impacted for the rule if a consistency snapshot is generated - less false violations will be reported therefore improving accuracy.
Other impacts of changes made in AIP Core 8.3.24
CAST Architecture Checker related
A bug has been discovered in previous releases of AIP Core Core: when Layers (created in CAST Architecture Checker (whether the standalone application or Architecture Studio in AIP Console) share objects (i.e. the same object is matched by multiple Layers), the number of violations reported by the rule in the CAST Dashboards was not correct. If the same link was violating the rule between two different Layers, only one was considered and sometimes the Layers were selected in a way which would change the results for the same model.
An example is shown below: the number of links between Layer L1 and Layer A2 (2 links) is less than between Layer L1 and Layer B1 (57 links). In reality, the number of links between Layer L1 and Layer A2 should be more than between Layer L1 and Layer B1 because B1 is a subset of A2:
Click to enlarge
This bug has been corrected in AIP Core 8.3.24 as shown below:
As a result of this fix, after an upgrade to AIP Core ≥ 8.3.24 the number of "overlapping objects" (those that belong to more than one Layer) will increase, and as a result, the number of violations of the associated Architecture Model rule will also increase - this increase will be visible in the CAST Dashboards.