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.
This RFE would require substantial compiler backend rework.
As a user, we would need to find a good balance between optimized and debuggable code; and weight its tradeoffs.
Ideally, users would have to use TEST.
Hence, this RFE is being rejected.
Problem is same for all dump analysis tools (and probably all trace debug tools).
Other problem : with OPTIMIZE(2), an indice (acces to an array) can be prematurally changed before all concerned statments are executed.
move var1 to array-var1 (I)
move var2 to array-var2 (I)
move var3 to array-var3 (I)
…
move varn to array-varn (I)
add 1 to I
Value of I can be changed (in data-item storage) before all move are executed, because value of I before incrementation is hold in register, and value after incrementation is already stored in memory.
Value stored in register should be the same as value stored in data-item... each time a value is changed in a cached-value in register, it should be immediately stored in data-item.
Registers should be use only for "repeatidly read value".
This RFE is being investigated further and will be updated accordingly.
If this issue relates to variable values being reported incorrectly, then shouldn't it be addressed as a bug (as a PMR) rather than a functionality enhancement (as an RFE)?