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:

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:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Dec 9, 2019

Improving the DBD management design

We had a Db2 load job run that used a load control dataset with 1,764 “INTO TABLE” statements run against a database that had one tablespace with 1,366 tables having 1,306 indexes. The DBD  length = 2628728.


When the job was run, the SYSDBDXA tablespace went from a couple of datasets to 79 datasets of 5,824 cylinders in size.


We opened IBM CASE #: TS002854455, but from the details it appears that Db2 is working as designed.


We were lucky that we did not see this in production and run out of datasets.

This could have been very painful. Our storage folks were adding volumes as fast as they could, but  we could have run out of spare volumes to add and lead to an outage.  We had to cancel the job and rerun it in smaller pieces. 

Needed by Date Dec 31, 2020