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 Future consideration
Workspace COBOL Compilers
Categories z/OS
Created by Guest
Created on Nov 2, 2023

Enterprise COBOL 6.4+ - Add sub-options to CONDCOMP(SKIPSRC) option to be more agressive in removing of lines concerned by conditional compilation

Hi,

The CONDCOMP(SKIPSRC) compilation option allows to remove lines in compilation listing of code excluded by conditional compilation.

Despite this, there may still be many lines related to conditional compilation present in the compilation listing (>>xxx directives) and which are not necessarily of interest to the developer.

These lines can be annoying when reading the compilation listing, and for what concerns us during debugging (which uses the compilation listing).

Indeed, we must consider two populations (at least in our context of implementing conditional compilation):
- the population of people responsible for managing a development framework, essentially in the form of copybooks implementing conditional compilation,
- the population of people who use this development framework and who do not need to go into the details of how it works (and should consider it as services).

We would like sub-options to be added to the CONDCOMP(SKIPSRC) compilation option:
1) a sub-option to exclude lines for compilation directives >>xxxx, with 3 values: keep lines from directives (default), exclude lines corresponding to conditional compilation conditions directives (>>IF, >> ELSE, >>END-IF, >>EVALUATE, >>WHEN, >>END-EVALUATE), exclude all lines of conditional compilation directives (including >>DEFINE).
2) a sub-option allowing to target the parts of code affected by the previous option, with 2 values: only to copybooks (default), to the entire compilation group (copybooks and main program).

Perhaps a combination of these two sub-options should be considered.

This operation should apply to standard compilations but also when using the MDECK(NOCOMPILE) option.

This should also apply to dwarf information stored in the loadmodule .


Attached, example of a program that uses a development framework in the form of copybooks using conditional compilation. The different files show the orginal program and different filtering of lines linked to conditional compilation as expected.

Thanks.

Idea priority Low
  • Admin
    Basil Kanneth
    Reply
    |
    Jan 29, 2024

    This idea is being accepted and will be updated once put into plan.

  • Admin
    Basil Kanneth
    Reply
    |
    Nov 28, 2023

    This Idea is being looked into further.