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.
For just one example, imagine a GETMAIN request that would not drive the region short on storage, but would put the region into a potentially "excessively committed" condition with regards to storage (the definition of "excessive" being that defined in the associated system policy). This mechanism could be used to deny the request.
The advantage of my suggested approach would be that it would allow selective enforcement of API access based on the current execution context - requesting user, or current system load, or any number of other potentially transitory states and metrics. Controlling at translation time would apply to "all users" and the only available user context would be that of the user executing the translate/compile. Please reconsider?
We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. Denying use of an API is best dealt with another way, for eaxmple by preventing it at translate time.