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
Thank you for your suggestion. While the requirement is for object level maximum locks held per thread, Db2 has delivered the similar capability but application level control in FL507. This is done through using built-in global variable, SYSIBMADM.MAX_LOCKS_PER_USER. Please review if this feature can be alternate solution for your requirement.
NUMLKUS is usually coded at a very high level and counts the total number of lock for the thread. I would like a parameter at a lower level - TABLESPACE - that behaves differently than LOCKMAX. Presently, lock escalation is the only effect of LOCKMAX. After that, you are depending upon NUMLKUS, which might be too high for your purposes.
This new parameter would be at the TABLESPACE level, and would specify a number of locks acquired at which point the thread would be cancelled - no lock escalation.
Could you please add more information - why the current NUMLKUS does not work for you. Today, we have NUMLKUS zparm to specify the max locks held per thread. Exceeding the value will receive resource unavail (SQLCODE -904 and message DSNT500I or DSNT501I are issued. ). thanks.