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.
Delivered in V6.1 February 2017 PTF
This RFE has been accepted and will be updated once put into plan.
Hmhm. Hans-Peter's comment has to be thought about.
Assuming the following situation: With executing an "uncorrect" statement you overwrite a field with the maximum range of a table ("hoops"). Afterwards you run into the next "hoops". But this "hoops" wouldn't happen if you have corrected the first "hoops" before. ;-))
Hello Hans-Peter,
the Statement should be executed.
Normally you run without SSRANGE, to the logic flow after violation always is unpredictable.
The Warning mode is to check programs, in the last times run without SSRANGE, now the first time with TableRange-Checking.
And if you get one ABEND, you don't know how much work you have to spent to the source code.
So, giving the chance to get all bad statements with just one run helps to estimate the amount of work to do.
Guenter
I would vote against this RFE. What is expected to happen, if a SSRANGE violation is detected: Should the corresponding statement be executed or bypassed? In both cases the logic flow after the violation will be unpredictable.