Differences between CodeReview, Software Analyzer and ZCodeScan and the future of each solution

[FALLAI-Denis]

Hi,

We purchased IDzEE licenses solely to use CodeReview (we're still in the implementation phase), while we only use VS Code as our editor.

Version 5.5.0 of IBM Z Open Editor now includes the ZCodeScan solution (currently very limited and actually unusable until it becomes possible to create your own rules).

Owning IDzEE licenses unlocks the advanced features of IBM Z Open Editor, and therefore provides access to ZCodeScan.

• Is ZCodeScan a new product or just a name change from CodeReview? (Apparently the implementation is not the same, especially on the z/OS side).

• What is the future of each of the CodeReview and ZCodeScan solutions?

• Is ZCodeScan intended to completely replace CodeReview?

• If both solutions are to continue, will they cover the same functionalities? What will be the differences?

• When is the functionality to create your own customer rules planned for ZCodeScan to be released?

Also, what are the differences between CodeReview and Software Analyzer?

Thanks.

[FALLAI-Denis]

Hi,

Since ZCodeScan is a shared feature of IBM Z Open Editor and IBM Developer for z/OS, is there a more appropriate site for reporting bugs or requests for enhancements to ZCodeScan itself? (The IBM Ideas site is more intended for enhancement requests, but not for reporting bugs.)
Perhaps it would be useful to create a dedicated GitHub space for ZCodeScan?
The IBM Z Open Editor GitHub site can continue to be used for requests regarding the integration of ZCodeScan into IBM Z Open Editor.

[phaumer]

We would be fine receiving them here. Another way would be to open tech support tickets.

[FALLAI-Denis]

Hi,

The new ZOE 6.1.0 version brings new default rules for zCodeScan 1.0.1, but they are not mentioned in the changelog.

The IDzEE documentation mentions these rules, but are they all available in ZOE?

• Added 51 new IBM ZCodeScan rules (49 for code quality review and 2 for security review).

https://www.ibm.com/docs/en/developer-for-zos/17.0.x?topic=zcodescan-whats-new-in
https://www.ibm.com/docs/en/developer-for-zos/17.0.x?topic=rules-cobol-code-review

For IDzEE, zCodeScan is now customizable, with the ability to create new custom rules. 🥰

• Codeless custom rules from regex 🤩
• Java custom rules 🤔

https://www.ibm.com/docs/en/developer-for-zos/17.0.x?topic=references-zcodescan-custom-rules-overview

Will this feature be available, at least at runtime, for ZOE? (We can agree to create personal rules in an IDzEE environment).

We were in the process of implementing CodeReview on z/OS for use during User Builds and for integration into our CI/CD pipeline (using the results from IBM DBB to call CodeReview).
Should we stop our work on CodeReview? Switch to zCodeScan?

The complete file of all zCodeScan rules is difficult to find:
https://github.com/IBM/idz-utilities/blob/master/ZCodeScan/Schemas/zcodescan-rules.yaml

Some of the choices on the default rules are surprising...
They would merit a discussion with the COBOL community for their implementation as a default rule, at least for their level of severity.

Rule: Avoid using level-88 entries in data descriptions
Category: Program Structure - Severity: MEDIUM

In COBOL, the Level 88 rule is used to define condition names that represent specific values or ranges of values for a data item.
It's used to make conditional logic more readable and maintainable by associating meaningful names with specific conditions, rather than hardcoding values in IF statements.
condition values ( level-88 entries) within data definitions leads to scattered logic, making maintenance and updates more complex.
Furthermore, the actual data values are abstracted behind condition names, reducing visibility and increasing the risk of overlooked changes during debugging or enhancements.

05    WS-ACCOUNT-TYPE PIC X(01).
  88  SAVINGS-ACCOUNT VALUE 'S'.
  88  CHECKING-ACCOUNT VALUE 'C'.
  88  CREDIT-ACCOUNT VALUE 'R'.
  88  LOAN-ACCOUNT VALUE 'L'.

IF SAVINGS-ACCOUNT OR CHECKING-ACCOUNT
  PERFORM CALCULATE-INTEREST
END-IF.

Thanks.