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.
A couple of suggestions for troubleshooting a scenario like this in the future. First, use the traceroute command from a remote system to confirm that network connectivity is at least good all the way to the router serving as a next hop for the z/OS system trying to be reached. And second, you mentioned that using packet trace on z/OS is hard to do. It should be as simple as using the VARY TCPIP,,PKTTRACE command, and specify filtering options to limit tracing to ICMP messages "PROT=ICMP" to the IP address you are trying to ping "IP=ipaddr". Once captured, you have the ability to convert the packet trace so that it is viewable from wireshark, if you are more familiar with that tool than IPCS formatters.