Provide table function that collects DSN1COMP data

Thank you for submitting this enhancement request. While we view all the enhancement requests we receive as valuable and we would like to implement all of them, in an effort to have maximum transparency we are closing the ones that don’t currently appear on our two year product roadmap. This is not to say that these enhancements may not still be implemented at some point in the future as we do evaluate our requirements on the basis of customer demand and technical impact, to deliver maximum value to our customers.

We appreciate your input to the Db2 for z/OS development team.  And we hope that you will continue to submit enhancement suggestions for improvements as customer feedback is a key component to shaping the future direction of Db2 for z/OS. 

Sincerely,

The Db2 for z/OS Team

Hello Bank of America. If it helps... I had a similar requirement to find a "better" way to review many indexes and pick the optimal pagesize.

My solution was to develop my little homegrown process/tool. Basically, my first job uses DSNTIAUL and SQL to examine catalog indexes for those that are "interesting" and generate DSN1COMP JCL where the DSN1COMP SYSPRINT output is sent to a concatenated dataset. I then submitted that generated JCL. The third JCL uses REXX to parse up the big DSN1COMP SYSPRINT dataset and transform the information into a simple flat file which I then LOAD into a table. At the end, I am able to "easily" query the table to see if the index is worth compressing and pick the optimal pagesize to minimize wasted space. At this point, one could query the final table again and use SQL to "generate" the required ALTER INDEX statements and "generate" the required REORG statements (depends upon environment)

I described these steps and give the JCL and REXX and everything in my IDUG presentations for 2020 in IDUG NA and IDUG EMEA. (yes, I did the same presentation at both virtual conferences). It will also be presented at IDUG Brazil and IDUG Mexico (in December 2020)

Obviously, my solution to this requirement is not as elegant as something like you are asking from IBM in this RFE. And your request is reasonable and interesting. But my solution worked for me and it streamlines some of the index-review process.... So it is better then a totally manual process! You could grab the presentation from the IDUG conference website... or email me and I can send a copy.

brian_laube@manulife.ca