IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 30 2019
  • Future Consideration
Why is it useful?
Who would benefit from this IDEA? Everyone who uses PBGs on z/OS.
How should it work?

The ALTER of MAXPARTITIONS should not invalidate any packages. I cannot even think what this ALTER  could possibly have to do with the access plan (path). The "new" PBR RPN *can* be ALTERed with a higher DSSIZE for TP and IP so I see no reason why PBGs cannot also be ALTERed like this.

Idea Priority Urgent
Priority Justification Auto rebind in production is *never* a desired outcome....
Customer Name Software Engineering GmbH
Submitting Organization
Submitter Tags
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    26 May 09:48pm


    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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    7 May 11:05am

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


  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    29 Nov, 2019 10:07am

    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...

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    12 Nov, 2019 01:59pm

    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.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Oct, 2019 02:35pm

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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Oct, 2019 01:49pm

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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Oct, 2019 01:41pm

    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 ?

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions