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.
This is definitely a sensitive setting within GDPS. I typically refer to PPRCFAILURE and PRIMARYFAILURE values as business driven settings, not at all to be changed by one person's desire, so I agree with the idea to make it a configurable dual control option. Other configurations within the policy management should remain as is, though: for example, when you site swap and need to adjust RPFC and Preferred Hyperswap (MM3SITE), we don't want to be restrict by a dual control enforcement here. Low priority.
Low priority - a warning message when it's changed would also be acceptable.
We believe that dual control is not so important here. But we would like to have something like a health check that tells us, if the policy has been changed (possibly by accident) and does not fit to our desired policy.
Again, needs to be configurable. But good idea to bring all configuration of production-type GDPS configs under dual control. Low priority this one.
good idea, low priority
It's very good idea, but not the most important currently. Low priority.
Worldpay has yet to pursue dual control rules.
Medium priority
Not the highest priority, as this is already protect-able. However, I (we) agree that all pervasive and potentially disruptive settings like this should ultimately be protected by dual control.
Definitely a good idea - Medium Priority
AmEx would like all the dual control functions that make sense, and this is another one.
LBG: This is a fantastic proposal, and it's something we'd like implementing within the next two years.