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.
See this idea on ideas.ibm.com
With HPF (HIGH PERFORMING FICON) and the CPU LOOP interactions with CACHED SOLID STATE STORAGE --- Generally speaking APPs on activation will (likely) incur a cache miss which is slightly longer than a CACHE HIT.
At any given time there can be a number of HITS (x) and MISSES (y) processing by storage and completed waiting on the "Ready List." A lot TRUER when operating IOPS above 64,000, 120,000 (or higher).
The READY LIST wait although short is troubling - MISSES having the longest wait (according to QMS) suggest the longest wait should always be worked first.
Working READY LIST from oldest ensures "new start UP apps" spend less time MOD Queuing.
CYDQ should list if the first Q'd IOB is a Write or READ - Helpful in telling which occurs how often ---
CYDQ0002W 15.04.42 1 RLT DASD MODULES AT OR OVER QUEUE COUNT 100 SDA MOD VSN DUPE SS USE/T SSID QUEUE* SERVTIME STATUS
2F4F 078D WW2518 078C BSS RLT/B 208C 100 606 NORMAL
END OF DISPLAY
Same for CYEM SNS- if it can tell which a write or read IO occurred last - currently it shows only the SENSE Command which isn't helpful when trying to determine which miss may have occurred last.
CYEM0099E 21.46.06 OVERRUN, CORRCTD, SSID-2064, DVC-2B08,TYPE-3390, CSW-0E00,CCW-3E,CHPID-98,SNS-04000000 08000028 00000019 13040014 0922007F 20642B01 000000E0 00000000
The above 2B01 is an IO timeout and is a request to re-drive the (read/write) IO on a different or same path - again can't tell (read/write) which IO is taking longer.
CYED needs to indicate if long-running IO is a read or a write... it's no help today.
CYED0012W 12.18.47 MODULE QUEUE FOR 29D0 MAY BE STALLED, SSID 204D, IOB 32C3EA00
Again these tools are of little help today - they don't identify the problem IO as being a READ or WRITE. Knowing helps to determine is more CACHE or CHANNEL separation required?
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This has been withdrawn by the originator.