This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
RACF stack affinity needs to be configurable for systems running with more than one TCP/IP stack. As of now, stack selection is indirectly influenced by access to EZB.STACKACCESS profiles in CLASS(SERVAUTH) and the order in which the stacks became active on the system. This leads to the following:
Invalid access attempts to stacks where no permit has been given to the RACF subsystem user. The more TCP remote nodes and stacks defined the more ICH408I messages are being written to syslog on every connection attempt, especially at subsystem start time (up to 100 in our installation).
Unsuccessful connection attempts with remote nodes getting stuck in "operative pending connection" state when access is granted to stacks other than the desired one and on which the destination IPs are not routable.
RACF itself should not be the component flooding the syslog with ICH408I messages when it's avoidable.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.