Release Notes - 1.1
-
1.1.7-funcrel
1.1.7-funcrel
Updated an internal library to provide improved resolution and compatibility with Python 3.9/Linux. -
1.1.6-funcrel
1.1.6-funcrel
1.1.5-funcrel
1.1.5-funcrel
All QRs have been given correct technology filter label: either PLC or PLI Now, the IBM PL/I analyzer does not depend on hard-coded “operator” role. Now, the IBM PL/I analyzer does not support Oracle or SQL Server as Storage Service. 💎 1001104 Weight for “Avoid PLI Main procedures using variables with ALLOCATE and without FREE (PL1)” has been changed from 0 to 1 💎 1001108 Weight for " Avoid PLC Copybooks using variables with ALLOCATE and without FREE (PL1)" has been changed from 0 to 1 💎 1001164 Weight for " Avoid Main procedures using the DATE builtin function (PL1)" has been changed from 0 to 1 💎 1001166 Weight for " Avoid Main procedures using the DATE builtin Function via include PLC (PL1)" has been changed from 0 to 1 💎 1001050 Technical criteria for 1001050: “Avoid Procedures and Functions using the ITERATE statement (PL1)” has been changed to “Programming Practices - Structuredness”. Previous technical criteria, “Complexity - Functional Evolvability” was removed from CAIP, which resulted in said QR never having violations. With changed technical criteria, QR will now have violations. 1.1.4-funcrel
1.1.4-funcrel
Missing link between PL1 Program and procedure 📝 21077 PLC Include PLC Include Correct Include Link will be created instead of incorrect call link Incorrect call links created from PLCInclude are now correctly be include links instead. Improved Detection Of PL1 File Structures Multiple PL1 file structures defined in the same statements are now detected. Improvement in Include links Multiple Entry statements would not correctly create include links to PLC