Skip to Main Content
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 Jun 25, 2019

Control of Locksize and Maxpartitions for implicitly defined tablespaces.

We must be able to control parameters like locksize and maxpartitions on implicitly defined tablespaces.
In DB2 V12R1M504 multi table tablespaces are deprecated, so we need to use implicitly defined tablespaces for QMF useres.  
Today we use segmented tablespaces with locksize table for these uses.
QMF users are business users with no control of commit scopes in their data manipulations.
Implicitly defined tablespaces use lock size ROW. It will cost us many lock request and lock escalations, so we want to control the locksize.
Implicitly defined table spaces use maxpartitions 256. We want to control the parameter as we well.