This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Enable to check maximum LATCH retention time in DB2PE reports etc
[Current Product & Version] -Db2 12 for z/OS -IBM Tivoli OMEGAMON XE for DB2Performance Expert on z/OS v5.5 -z/OS v2.3 -WebSphere Application Server v9 for z/OS
[Environment] Data sharing in three-way sysplex environment
[Problem] Our customer is using WAS for z/OS and DB2 for z/OS on their mission critical system. Several times our customers experienced slow transaction responsiveness and timeouts, severely impacting their business. I opened CASE(TS013070610/TS013085686）to resolve this problem, but these CASEs does not identify the cause of the problem and does not currently resolve the problem.
This CASE explained that some read thread held S page latch waiting, it could cause the index split thread to wait on the page latch, so many transactions became wait or time out. Unfortunately, it was not possible to identify the read thread holding S-LATCH for a long time from materials such as Db2 logs.
As a side note, obtaining SLIP dumps using SLIP traps is not acceptable due to concerns about reduced transaction response. We believe that product improvements are necessary to identify the cause of this problem.
[Proposal/Idea] We request improvement so that we can know the maximum retention time of LATCH during transaction execution in the DB2PE accounting reports, etc.
[Benefits/Value] Our customers can identify the cause of this problem, consider a solution, and expect normal and stable business operations.
Do not place IBM confidential, company confidential, or personal information into any field.