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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
We've delivered the doc updates for this RFE in V6.2 and V6.1 updates in the KC at:
https://www.ibm.com/support/knowledgecenter/SS6SG3_6.2.0/com.ibm.cobol62.ent.doc/PGandLR/ref/rldirinl.html
and
https://www.ibm.com/support/knowledgecenter/SS6SG3_6.1.0/com.ibm.cobol61.ent.doc/PGandLR/ref/rldirinl.html
With Cobol V62 "May 2018", the inlining of PERFOM causes anomalies during the execution in trace mode and on the analysis of the dumps: the correspondences between source line number and address of the instruction are corrupted around the lines concerned with the inlined PERFORMs.
"NOINLINE" partially solves the problem, except for paragraphs that have been performed only once and which are always inlined despite the "NOINLINE" option.
The ">>inline (on|off)" directive may have been created to handle the inlining of several times PERFORMed paragraphs (mastering the size of the binary code), but the control of the inlining must be independent of number of PERFORM calls to a paragraph and must also apply to single time PERFORMed paragraphs.
One may wish not to "inline" technical routines at the heart of the "business" binary code (to facilitate the debug for example, or because these technical routines are not always called to the execution because conditioned).
This RFE is being accepted as a doc update. The following update will be made to the documentation:
"The word inlining here implies that the compiler might choose to replace the PERFORM of a procedure (paragraph or section) that is performed more than once with a copy of that procedure's code. By inserting the procedure code at the location of the PERFORM, the compiler saves the overhead of branching logic to and from the procedure. Note: if a procedure is only performed once, the compiler might move the code for that procedure to the PERFORM site, even with >>INLINE OFF."
This RFE is still under consideration
Attachment (Use case): Listing
Attachment (Use case): Source code