IBM Z Software
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).
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.
Joe's email comments: 3/10/2025
***
I think the priority level should be "high", not "medium".
State Farm, Northwest Mutual & USAA are 3 cloud customers using zHyperLink writes. The ZHL write response is very much a function of write transfer size. With the current (DS8950F and DS8A00) implementation up to 2 tracks (96K) can be written in a single ZHL write operation. For the DS8950F, the 4K ZHL write response time is ~30us. SO far so good. But at 25K the ZHL write response time is ~100us.
Plus there is a distance penalty (not sure how we handle that!). Plus DS8A00 allows reads up to 32KiB (default is 16KiB).
We could also improve reporting. The table given for PFIDs could be improved (I should use Todd's method for that). What also needs to be done is to add variables (and use them) that includes the overhead of failures into the successful ZHL processing time. This can be done only with the 74.1 data.
Finally, (for ZHL!) we could also ingest and report on DS8K ZHL metrics. The per port metrics are important to show the disparity of performance based on the port connected (DS8950F anyway). Some ports have an extra "hop" thru a PCIe switch and it's measurable (3us-5us).