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

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 (

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 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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Under review
Workspace Db2 for z/OS
Created by Guest
Created on Feb 21, 2023

Correct wrong data in IFCID0172 QW0172HQ/QW0172Q1 when package changes occur during waiting/deadlocking

The issue is that

1.- Thread 1 and Thread 2 get locks

2.- Thread 1 changes packages

3.- Thread 1 and 2 deadlock

4.- Thread 1 is chosen as blocker and deadlock processing uses user data from Thread 1's waiter, but

the package dependent information is incorrect for the holder/blocker because Thread 1 changed

packages before waiting/deadlocking


Db2 and IRLM don’t currently have any sort of tracking for package changes that we could use to get

the correct information during deadlock, so the way we’ve decided is best to try and move forward is

to change Db2 lock requests to pass package information to IRLM and update IRLM structures to save

the info in case the lock becomes involved in deadlock. However, there are potential performance issues

with adding this tracking. 

In the meantime, customers should be able to use the stmtid to search the sysibm tables for most

of the package dependent information if the blocker used static SQL. We get the stmtid when the

lock is requested, so it will be accurate when the blocker is reported.

Needed By Yesterday (Let's go already!)