IBM Z Hardware and Operating Systems Ideas Portal
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).
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.
Med priority: Good idea, would definitely support a GDPS healthcheck implementation of this feature. Having the ability to specify a minimum number for online secondary paths could reduce a lot of noise, whilst protecting sufficient connectivity.
Yes, it is important to monitor the access to the secondary devices to prevent additional problems after an unplanned hyperswap when I'm in a critical situation already. The check could be done in a customizeable check to allow the loss of some paths ("orange alert") or a critical amount of paths ("red alert"). Prio: high
We find it important to be able to rely on consistency by failover. Like using heatmap transfer so after failover there is no/little impact when having your I/O's in RS2.
You don't want to find out you'll be having less capacity at a moment you have an unplanned hyperswap. You can't go back (yet), having a new problem to solve first to keep the business up and running, before you can focus on restoring the cause of the hyperswap.
Doing it by GDPS HealthCheck as alpertec mentions, each company can choose to use it or not (could be a choice to have different amount per site). I think should be configurable to what is acceptable for the company (i.e. 8 paths in RS1 and minimum 3 in RS2)
I agree, however in my opinion, this can also be handled by a GDPS HealthCheck
LBG support this. High priority.
Unless/until GDPS zOS Proxy implements the check for secondary devices paths, this support wouls not be meaningful for us.
We'd consider this as a high priority RFE to also avoid the mentioned problems after HS (our CommsDevices are always gen'd offline@IPL).