Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Jun 1, 2021

Enterprise Cobol - Reconciliation between Listing line number and Source line number

We are in the process of deploying the implementation of a DevOps approach on the mainframe.

In particular, we want to implement code coverage and unit test follow-ups (automated tests).

Market tools, especially the SonarQube tool, work with the Source code line number, but code coverage tools typically return the line number in the compilation Listing.

We would like to have an utility that transforms a compilation Listing line number into a Source code line number.

We would be able to develop such an utility (this is a simple file pairing problem), but we believe that this utility should be provided with the COBOL compiler in such a way that it is universal and usable in any environment for any solution for each of the customers.

This utility should also take into account the detection of dead code (unreachable code) and uncompiled code (code excluded by conditional compilation directives).

An alternative would be for the COBOL compiler to keep track of the Source code line number and be able to return it to the compilation listing level, but that would mean that the COBOL compiler would be the only source code processing process, which doesn't This is not the case when using pre-processors (Db2 or CICS) which themselves transform the initial source code.

The utility should produce a file containing at least for each line of Listing the following information:
- Listing line number
- COBOL division: Identification, Environment, Data, Procedure
- origin of the line: main source, COPYBOOK, pre-processor ...
- Main Source line number (null if the line does not come from the Source code: COPYBOOK origin, pre-processor ...)
- kind of the line: comment, non-procedural (without associated executable code), dead code, code excluded from compilation

Idea priority Low
  • Guest
    Reply
    |
    Jul 8, 2021

    The code coverage and SONAR context is just a use case.
    We believe there may be many other cases where tracing / tracking the source code line number may be necessary.

    With modern tools, the developer rarely consults the compilation listing, and he is satisfied with just knowing the return code of the "build", (which poses other problems because then he does not take cognizance of the Warnings such as for example the messages emitted by the RULES).

    Regarding your answer, what tools do you recommend to deal with code coverage with restitution of the line number in the source code rather than the line number in the listing?

  • Guest
    Reply
    |
    Jun 29, 2021

    This RFE is being rejected with the suggestion of using a code coverage tool that's compatible with Enterprise COBOL.