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

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 erroneous numbers of violations were being reported:

• In the code below, there is no MOV from "a sign numeric to a non-sign numeric" and yet a violation was reported by the rule - this violation is false and has been fixed:

PROGRAM-ID. HELLO-WORLD.
DATA DIVISION.
    WORKING-STORAGE SECTION.
        77 X PIC -999.
        77 Y PIC S999 BINARY.
PROCEDURE DIVISION.
MOVE 123 TO X.
DISPLAY X.
MOVE X TO Y.
DISPLAY Y
STOP RUN.
}

• In the code below, there is a MOV from a sign numeric to a numeric, however no violation was reported by the rule - this violation is in fact true and has been fixed:

Move 10 WS-CIRCI00O-WRITE-CNT PIC S9(09). Example : -123456789
To WS-IRC-RECS-WRITE-NUM PIC Z,ZZZ,ZZ9. Lost of data: 1,234,567

As a result of these fixes, results may be impacted for the rule if a consistency snapshot is generated - less false violations will be reported, but at the same time, new true violations may also be reported - both improving the accuracy of this rule.

Other impacts of changes made in AIP Core 8.3.21

Mainframe

Improvements have been made to syntax coverage for IBM MQSeries and Cobol as listed below. As a result of these changes, some impacts to existing results may occur when performing a post upgrade consistency snapshot - change in the number of violations, transaction/function point values etc.

IBM MQSeries updates

Syntax coverage has been improved when using data from JCL. The following is now supported:

• FROM instream data SYSIN when using DB2 utility to call PGM - ACCEPT
• FROM PARAM when Exec Program

Cobol

The following syntax is now supported:

• ACCEPT verb for processing data passed as input to Cobol programs via SYSIN
• Data passed as input to Cobol programs via PARM

CAST Transaction Configuration Center

Items that are considered datafunctions of a transaction

Previous releases of CAST Transaction Configuration Center did not recognize certain object types to be datafunctions of a given transaction. This has now been updated and the following objects are correctly recognized as datafunctions of a given transaction:

• COBOL file
• COBOL database
• COBOL database segment
• Data functions defined by type inheritance of category "APM IFPUG Data Function"

As a result of this fix, some impacts to existing results may occur when performing a post upgrade consistency snapshot: FTR (File Type References) values may change.