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.
We have encountered multiple issues during our transition to z16 where either MCL cause the conn. to go away and we have also had an issue where the SE was in a weird state and IBM had to reboot it. Earlier this week, we had a service network switch flake out and we received the PERM COMM errors. I agree it would be much simpler if we could know as soon as the local CPC connectivity is re-established so we can trigger a refresh or recycle of our process.
Currently the "comm available" hardware event requires registration, which was terminated to our application when communication was lost. The "comm available" event is not seen, sometime until hours later, when we are able to determine all is well and re-register for events. Not useful for a timely recovery. We would like to see a WTO issued when communication is restored to allow automation to be triggered to automatically re-connect and register to the impacted CPC.