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.
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.
|Priority Justification||Auto rebind in production is *never* a desired outcome....|
|Customer Name||Software Engineering GmbH|
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 "firstname.lastname@example.org" 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