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.
Thank you for the information.
An INSPECT TALLYING statement with a zoned decimal counter only requires at most one conversion between zoned and binary in each direction, which is cheap relative to the cost of the INSPECT TALLYING itself. This is different from cases like a subscript, in which the cost of converting from zoned to binary is by far the most expensive part of the subscript operation. The loss of performance from using a zoned decimal counter is not large enough to justify a RULES(NOLAXPERF) message. Hence, we will be rejecting this RFE.
Hi well test case is any INSPECT TALLYING statement the counter contained in the instruction may be underperformant is not in packed or binary format.
Hi RULES(NOLAXPERF) don't inspect the counter used in INSPECT TALLYING STATEMENT as it does for subscripts. As this data must logically be a binary or a PACK-3. I think that the program is under performant witn an counter coded in zoned decimal. So why rules(nolaxperf) isn't pointing it out ?
What case are we looking for here? Is a testcase available?