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 Mar 5, 2019

Cobol - New Reserved Words to reduce hard coding

My suggestion is Cobol should have two new reserved words containing the currently executing Section / Paragraph name i.e. CURRENT-SECTION / CURRENT-PARAGRAPH (both would have an implicit picture clause X(30). Typically this would be useful in error scenarios.

Idea priority Low
  • Guest
    Reply
    |
    Jun 22, 2020

    Hi, since we have not received any feedback, this RFE is being cancelled. Feel free to open a new one if you are able to answer the previous questions. Thanks.

  • Guest
    Reply
    |
    Jun 3, 2020

    May we know if you got a chance to review our April 14th, 2020 update?

    We shall keep this RFE open till June 17th, 2020 after which we shall close it if no response by then. Thanks.

  • Guest
    Reply
    |
    May 27, 2020

    May I know if you got a chance to review our previous update?

  • Guest
    Reply
    |
    Apr 14, 2020

    CURRENT-SECTION / CURRENT-PARAGRAPH may not make sense when we optimize. But we could do the Program name and line number. May we know if that is sufficient for your case?

    Thanks.

  • Guest
    Reply
    |
    Jun 6, 2019

    Thank you for your response. First, if you determine the suggested options are 'special registers' then so be it. Next, I am unclear what you mean by 'no-inlining option'? Finally, the reference to 'compiling in production' makes no sense to me - why would production be different? (many programs abend in a controlled fashion in production and development environments so accurate diagnostics are important)

  • Guest
    Reply
    |
    Jun 5, 2019

    Hi,

    After investigation, we have determined that these are more of special registers instead of reserve words.

    This would likely have to be a no-inlining option. As a result, this would not help when compiling in production. Is that ok?

  • Guest
    Reply
    |
    Apr 27, 2019

    Dennis, Thanks for your comment. My background is Enterprise Cobol on z/OS. The aim of the suggestion is to reduce possibly erroneous hard-coding by introducing new reserved words. If I understand your comment correctly identifying "context of the exception's origin" would still involve hard-coding in order to derive current values.

  • Guest
    Reply
    |
    Mar 18, 2019

    This RFE is being investigated further.

  • Guest
    Reply
    |
    Mar 6, 2019

    I think that for this need it would be better to implement exception handling and have an instruction to trigger an exception.The context of the exception's origin (current section, current paragraph, current statement, etc.) should be included in the data passed to the exception handler.