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.

Add a new idea Subscribe
Status Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Sep 29, 2016

RELATED IDEAS

Show inserted CICS elements as part of the source code COBOL listing

When compiling with the COBOL co-processor, when CICS elements DFHEIBLK and DFHCOMMAREA are not coded by the programmer they are inserted by the compiler into the LINKAGE SECTION and as parameters on the PROCEDURE DIVISION statement.
The elements do appear in the data mapping section of the listing but do not appear as part of the source program listing.
This can be confusing and mis-leading when reading the compile listing and when following parameters passed from a calling program to the called program.
Therefore these elements should always be shown in their appropriate places in the source code listing.

Idea priority Medium
  • Guest
    Reply
    |     Nov 7, 2016

    We have several problems implementing this requirement.
    1) First the listing output will be different then the Mdeck output. The debugger use the Mdeck source but the debugger breakpoints are based on listing statement number.
    2) Secondly the current compiler design eliminate all generated code from showing up in the listing. We don't have a way to exclude "some" of the generated code.

    Rejecting due the above causes.

  • Guest
    Reply
    |     Oct 12, 2016

    Suggestion : on option, show code and data items generated by coprocessors ( CICS and DB2 ) in Source Listing as "comment lines" with a special character in column 7, or other marks.
    This can help to understand some logic like "exec sql whenever ... goto...".

  • Guest
    Reply
    |     Oct 12, 2016

    Same problem with DB2 coprocessor and SQL--* data items.
    Theses data items are not explicitily referenced by Cobol source but are used in code generated by coprocessors and usefull for debuging...
    Note : our debugger (Macro4 suite) show these data items as "automatic data".

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.