This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
HAA did not pick up the need for NPSIs to be reorged when TS was being reorged
SEMHNSA TS partition 278 having 2 NPSIs was triggered for REORG. HAA is run 6 times on Saturday and 4 times on Sunday since this TS is so large, 7 billion rows in some environments. REXX code rebuilds the RGNSA001 so that only 100M rows are reorged (submitted AHA for this):
RGNSAALB - generate reorg JCL
RGNSA001 - reorg job
The second cycle generated a reorg for the two NPSIs. My issue is why was this not included in cycle 1 job. If this wasn't run multiple time back to back the NPSIs would never have been reorged where stats could be taken. An issue was found in the profile where stats were not being taken for index reorgs, RGNSA001 J0310165. This has been corrected.
Do not place IBM confidential, company confidential, or personal information into any field.