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.
Good idea, but in our case it would need to be a very long history if it only had hyperswap information. Maybe more useful to us as part of an events history log, that holds information like script start and end times, replication interruptions, etc, as well as hyperswaps. It would save time trawling through old Netview logs looking for that type of information.
I think GDPS lacks some type of Audit Log in general. This is one good example, but scripts execution in general could also be looked at for storing historical important events.
I use SDF exit to log scripts execution so we can track the Hyperswap execution among others, but I submitted idea ZGDPS-I-245 to make it something officially supported.
low priority.
Good idea.
It's very good idea, but not the most important currently.
Low priority
Worldpay also likes the idea of having some HS history within GDPS. This would be the 'source of truth' in addition to records in Incident Management.
This will be handy for checking when hyperswap had happened - Low priority.
Would be useful for tracking and comparison purposes without having to maintain a separate document.
We'd also like to see the phases of HS in any solution implemented along with UIT - Priority Medium
LBG: This is an excellent idea and something we would like in the next two years.
It may also keep information about Freezes (both planned and unplanned)