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 Oct 10, 2020

Enterprise Cobol V6+ - comment directive

We suggest implementing a "comment" compilation directive.

This could be the >>* directive.

This directive would allow comments to be introduced in a source code, which would not be returned to the compilation listing (so as not to overload it).

Idea priority Low
  • Guest
    Reply
    |
    Feb 9, 2022

    Workaround solution :

    *CONTROL NOSOURCE
    * explanation of what do this copybook and why
    * bla bla bla
    * bla bla bla
    * replaceable parameters :
    * :p1: for parameter 1
    * :p2: for parameter 2
    * changes history
    * 10/10/2020 : me
    *CONTROL SOURCE
    some code

  • Guest
    Reply
    |
    Nov 24, 2020

    >* : comment present in compilation listing (application / functionnal comments for developers)
    >>* : comment removed from compilation listing (internal comments for framework maintenance in copybook)

  • Guest
    Reply
    |
    Nov 5, 2020

    I think my request was not understood.
    I want to have a function allowing me to comment on souce code without these comments being visible in the compilation listing.
    This concerns in particular the technical comments introduced in a COPYBOOK intended for the maintenance of the COPYBOOK but which do not necessarily concern the user of the COPYBOOK.

  • Guest
    Reply
    |
    Nov 2, 2020

    This RFE is being rejected. Please use the solution mentioned in comment 1

  • Guest
    Reply
    |
    Oct 20, 2020

    Hi Rune

    Comment directive, >>*, is for internal documentation for framework maintenance .

    These comments are not for developers.

  • Guest
    Reply
    |
    Oct 12, 2020

    Hi Dennis,

    There is allready the possibility to make comments like you suggest.
    You can even make floating comments like this: *>
    I disagree with the request that the comments should be removed from the compilation listing, as the comments can be very useful when debugging using the compilation listing.

    If needed, it should be a compiler option to remove comments from the compilation listing.

    Regards,
    Rune