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 for z/OS
Created by Guest
Created on May 20, 2021


I love the upcoming FL508 and this new availability even though I have not used it. Looking deeper into the Knowledge Center there seems to be some limitations that I would like to see resolved.

The two items are:

a) Exist in the same database as the source table space

b) The source be a simple or segmented (non-UTS) table space whereas target be a universal partition-by-growth table space.

Two examples would help justify this need.

1) Some users (not necessarily us) have huge amounts of tables in a single tablespace. Spawning those out is a great feature in FL508 but the requirement to keep in same database is not ideal because there may be database level locking and I can see a future alter failing for that reason.

2) We have some PBR tables in a database that are very heavily used. It would be nice to move them to a new database. I'm not sure why we are held to PBG and of course same database. Moving those around would help reduce database level locking.

I'm sure there are other reasons for enhancements to this brand new feature but again thank you for providing the first round of functionality in this feature.

Needed by Date Jan 1, 2022