IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.
Additional Information:
  • The shorter URL for this site is:
  • To view our roadmaps:
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

New DB2z "LOCKMAXCANCEL" tablespace characteristic - cancel thread when N locks have been reached

Suggest a new parameter for the TABLESPACE definition (perhaps named "LOCKMAXCANCEL").


This would allow you to specific a number that represent the maximum number of locks that can be acquired for the tablespace at which point the thread would be cancelled (i.e. resource unavailable).

  • Seth Bienstock
  • Dec 15 2018
  • Need More Information
Why is it useful?
Who would benefit from this IDEA?
How should it work?

Proposed Solution:

A new sub-parameter of LOCKMAX, coded as follows:


When a non-zero value is supplied for LOCKMAX, you can optionally code "CANCELTHREAD" which would mean that instead of lock escalation occurring, the thread is cancelled.

Measurable Benefits:

There have been times where a call results in too many locks being taken on a heavily referenced table and the thread continues for too long thereby locking other threads out. This is usually caused by poor application design/coding, and sometimes just due to the (state of) the data at the time. For those infrequent, but costly, occasions where this occurs, this capability would help prevent this from happening.

Current Work Around:

None at this time.

Considered customizing a third-party monitoring tool to identify the situation and cancel the thread. This would result in additional overhead and would probably be a bear to maintain from a DBA/admin perspective.

Idea Priority Low
Priority Justification
Customer Name Morgan Stanley
Submitting Organization
Submitter Tags
  • Attach files
  • Seth Bienstock commented
    28 May 12:42pm

    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.

  • Admin
    Janet Figone commented
    29 Jan 07:51pm

    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.

  • and 16 more

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions