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 (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
Dear Matthew, Thank you for submitting this enhancement request. Our Db2 for z/OS development team continues to review this and believes, with some modifications, they can accept the idea. Please see the below feedback they provided for you and let us know your thoughts:
The commit-LSN is maintained for each object, but there could be over 100,000 objects.
Each Db2 member that is modifying the object maintains the commit-LSN for the object.
Always calculating which Db2 member is holding up the commit-LSN for each object would be too much of a performance overhead. There are thousands of objects. Plus, the Db2 member that is holding up the commit-LSN for the object could be constantly changing.
There is no member scope commit-LSN maintained for all objects. The Db2 code has no use for such a member scope commit-LSN.
We cannot issue a message for the Db2 member that is holding up the commit-LSN, but to monitor for cases where the commit-LSN is not advancing as expected, a combination of the following methods can be used:
1) Look for a new message that's issued when the V12 commit-LSN enhancement is disabled. One of the actions would be to check for a Db2 member that was last started with restart light.
2) Look for existing messages such as message DSNJ031I WARNING - UNCOMMITTED UR HAS WRITTEN number LOG RECORDS and message DSNR035I WARNING - UNCOMMITED UR AFTER number CHECKPOINTS. These long running URs are holding up the commit-LSN.
3) Issue the -DISPLAY DATABASE command with the LRSN option to display the current commit-LSN for the object. The documentation for the LRSN option needs to be updated. We can also consider enhancing the LRSN option to report the commit-LSN from each of the Db2 members.
Sincerely,
The Db2 for z/OS Team