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 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,
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
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
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?
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 feature is in OMPE and will not be implemented.