Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Created by Guest
Created on Jun 22, 2022
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit DB2ZOSTLS-I-32 enable queryno for static SQL in cqm tables RFE 126827.

Display the blocker query in Timeout/Deadlock situations Merged

DB2 Timeouts and Deadlocks can cause significant problems for applications, and resolving them quickly is a high priority. Identifying the query that caused the deadlock or held locks long enough to cause a timeout is very important, with this info DBAs can quickly check access path and determine if we can tune it to avoid future deadlocks and timeouts.

DB2 Deadlocks and Timeouts result in SQL error -913. CQM captures information for the queries that are victims of the deadlock/timeout, but the winner/blocker queries complete successfully, and CQM doesn't make it easy for us to identify which query blocked access and caused a deadlock or a timeout.

DB2 Address Space provides the following information:




153 LUW-ID=0AD01111.BB3E.220613160708=46917







153 LUW-ID=0AD01111.E91F.220613164950=69333




So it provides the number of the blocker query in the Dynamic Statement Cache, in this case - 1663. The problem is that we can't easily dump the cache when the timeout occurs, and by the time we dump it, the statement is often not in the cache anymore.

Here is our request: when we investigate a deadlock or a timeout, we want to be able to find the blocker query in the Current SQL Activity or in the Activity Summary for the right timeslot. DB2 knows the query (in the Address space it displays query number), so we would like to either add a Query Number column to CQM output, or have another easy and intuitive way to find the blocker query text.

Considering the fact that we sometimes investigate timeouts the next business day, it is important that this info is collected and kept in CQM. OMEGAMON is not the right tool for historical info.

Thank you.

Needed By Quarter
  • Admin
    Megan Yee
    Aug 1, 2022

    Thank you for your enhancement request. We plan to complete the work started on DB2ZOSTLS-I-32 and will focus on the QueryNo part of this idea. This idea is merged into DB2ZOSTLS-I-32.