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 Future consideration
Workspace Db2 for z/OS
Created by Guest
Created on Dec 28, 2021

Prevent SPT01 growth with new behaviour REBIND(EXTENDED) in Cod-Level M510

Before Codlevel M510, PHASEIN functionality was only used when the package was executing

Since the implementation of Codlevel M510 (include PTF 73874 (APAR PH28693)), executing a REBIND with PLANMGMT(EXTENDED) will always store information in SYSPACKCOPY and SPT01, even if the package is not executing, increasing strongly this main tables.

Afterwards, we can clean those copys with the new FREE PLANMGMTSCOPE(PHASEOUT)

Db2-IBM-Lab suggested to open an Idea:

We wonder if Db2 could try to make automatically this FREE PK PLANMGMTSCOPE(PHASEOUT) after each REBIND PK(EXTENDED), so Cat&Dir shouldn’t increase that much.

Only those PK that couldn't be Freed in that moment would remain with that copy in the Catalog.

In summary if Db2 could make REBIND(EXTENDED) of one PK, and just afterwards, the Free PLANMGMTSCOPE(PHASEOUT) of that PK, if possible, and so on.

If this method is complex, another solution could be a Subtype of REBIND(EXTENDED) with previous behavior; something like REBIND PK(EXTENDED) COPY(USE / ALL).

Or any other that you consider better.

Thanks in advance for your help and Db2 improvement

Needed By Not sure -- Just thought it was cool