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 Oct 30, 2019

Stop package invalidation after ALTER MAXPARTITIONS

These days in an agile world we have to ALTER PBG spaces on-the-fly to raise the MAXPARTITIONS value. Sadly this ALTER, even though it is an immediate ALTER, sets all dependent packages to VALID = 'N' which is, of course, a disaster.

Needed by Date Jan 31, 2020
  • Guest
    Apr 7, 2021

    But for PBGs there are no key ranges at partition level!

  • Guest
    May 26, 2020


    So yes, parallelism can put key ranges into the access path, and so can limited partition scan. Reorg rebalance, insert partition, alter table rotate part,

    Best regards,

    Pat Bossman

  • Guest
    May 7, 2020

    A similar issue occurs with the Reorg Rebalance, why does it set VALID='N' for all related packages?


  • Guest
    Nov 29, 2019

    ahh now I understand why MAXPARTITIONS can have an impact. But at what level? If I define a MAXPARTITIONS at say 256 is it seriously going to assume I can run with 256 parallel sub-tasks?? Surely not! I could believe this with up to 16 but above that I cannot really think it is ever used...

  • Guest
    Nov 12, 2019

    Per IBM the reason that the packages are invalidated due to parallelism.  But I'd like to recommend that if the packages are bound with Degree(1), that they are not invalidated.  

    When parallelism build a parallel group partitioned on page range, it will use the current defined MAXPARTITIONS as the high bound (the maximum partition or pages can the table have). So, when MAXPARTITIONS increase, then any newly added partitions will be out-of-the-parallel-group-scan-boundary. Hence, causes incorrect output (whatever the data resides in the newly added partitions, will never have a change to be examined). In order to correct the behavior, we request the previous bound parallel plan to be rebound(invalidate the package for a rebind) to make sure we cover the newly defined/added partitions.

    On the other hand, if the MAXPARTITIONS is decreased, then the parallel group will still cover the whole range and Date Manager guarantee that if the needs to be scanned page/partition is over the maximum physical page/partition, it will simply returns EOF. So, no re-bind needed in this path.

    Hope this answer your question. Please let us know If you have any further question or concern.

  • Guest
    Oct 30, 2019

    With only impact to catalog, not sure how Access Path would be impacted.  Seems wasteful and counter productive to invalidate packages.

  • Guest
    Oct 30, 2019

    I opened a Case on this asking why packages are being invalidated in this situation and it is still open waiting for a reply.

  • Guest
    Oct 30, 2019

    this is just a limit in the catalog.  So how could access path be affected ?  The actual growth of a partition doesn't invalidate the package so how just changing the limit do so ?