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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Db2
Created by Guest
Created on Nov 2, 2020

DB2_FORCE_APP_ON_NUM_LOG_SPAN

Please provide a registry var DB2_FORCE_APP_ON_NUM_LOG_SPAN

similar to DB2_FORCE_APP_ON_MAX_LOG.

Needed by Date Jul 1, 2021
  • Admin
    Michael Roecken
    Jan 8, 2021

    The primary usage of NUM_LOG_SPAN is for kicking out transaction that sits idle for long time. So forcing off the problematic app is the only option, as it is not doing anything so we don't have an opportunity to return an error like SQL0964 to trigger the application to issue COMMIT or ROLLBACK. The only possible implementation would be to delay the forcing off of the problematic application after detecting it has exceeded NUM_LOG_SPAN, to give it a chance to execute some new request within the delay, so we can return error such as SQL0964 to trigger the application to issue COMMIT or ROLLBACK. This would be like to provide new DB2_TIME_TO_FORCE_APP_ON_NUM_LOG_SPAN for user to set such delay. This behaviour is not ideal in that it does not guarantee the problematic application will not be forced off, and the delay can cause undesirable impact to the other applications executing on the database. So the decision is to reject this request.