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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Confer to « PH35652: IMPROVE COBOL OFFSET REPORT USABILITY » fix for Enterprise COBOL V6R3.
Hi,
What other clients have been doing for this kind of scenario is to use OPT(0) for debugging purposes; and then use higher opt for production.
Please consider using this a solution to this RFE.
Unfortunately, it won't be possible to have a fully debuggable optimized binary.
Thanks.
Thank you for your recent update. We are reviewing it and will update you shortly.
Programs tested with Compuware Xpediter / Abend-AID, and Macro4 TraceMaster / DumpMaster.
Options: OMTIMIZE(1), NOTEST, INLINE, OFFSET
Lack of informations in OFFSET/LOCATION doesn't permit de trace / debug inlined statements (if same statements are inlined more than once) : same statement can occurs several time in binary code, but get only one OFFSET/LOCATION, so debugger can't identify Cobol inlined statement in trace or abend.
Problem exists also for PERFORM statements that are not reported with good OFFSET/LOCATION.
May we know which tools your currently using that has these issues?
If CPW, you will have to get in touch with their devs to analyse this. The CPW devs can contact us if they think this is a compiler bug of some sort.
Note: when compiling with OPTIMIZE(1) + TEST(NOEJPD) options, the locations assigned to PERFORM statements that are inlined are correct, (they correspond to the first statement of the inlined paragraph), and the generated binary code is identical to the binary code generated with the OPTIMIZE(1) + NOTEST options.
Attachment (Description): Sample program compiled with INLINE and OFFSET option
Attachment (Description): Sample program listing compiled with INLINE and LIST options
Attachment (Description): Sample program