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 Not under consideration
Created by Guest
Created on Oct 29, 2019

DSNT376I messages reintroduced

With introduction of APARs PH08708 and PH08431, messages DSNT376I are suppressed.

These are the sentences:

PH08708 -> When Timeout Exit is called, IRLM may flag that no DSNT376I message should be issued. In this situation IFCID 196 records will still be written but there will be no DSNT376I message on the console for these additional waiters being timed out.

PH08431 -> During this time period, the msgDSN376I will be suppressed while the IFC196
continues to be cut.


Now the db2 DB2MSTR joblog no longer reports all DSNT376I messages that correlate a timeout / deadlock with the contender and therefore it is difficult to quickly identify the origin of the contention.

The QM, in section 2 (View SQLCODE) implements the display of these but also in v330 (expanded with respect to v320) there is no reference with respect to the contender.

 Is it possible to expand this function to get this information?

  • Admin
    May Chu
    Jul 17, 2020

    This feature is in OMPE and will not be implemented.