Skip to Main Content
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 Apr 30, 2020


Recovery to PIT or to current, and non-standard recovery methods such as DSN1COPY or DF/SMS dataset DUMP/RESTORE from flashcopy backups can leave TOTALROWS set to 0, NULL or invalid values. Trying to run something like a REBUILD index relies on TOTALROWS to determine required sort space so having a good value in TOTALROWS is important. A REORG on very large TSs or when a customer is trying to recover a production table as quickly as possible is not always feasible. Running RUNSTATS SHRLEVEL REFERENCE without SAMPLE is also frequently not feasible because it takes a long time and uses a lot of mips.

Currently for RUNSTATS using row sampling via the SAMPLE keyword I understand that there is no technical reason why RUNSTATS cannot update RTS TOTALROWS/DATASIZE, since RUNSTATS still reads and processes every row.

I am told, however, that the strategy going forward might tend more towards page sampling as we do now with TABLESAMPLE.

Since TOTALROWS is so important for utilities, and since the current design of RUNSTATS easily supports updating this value I am, on behalf of Walmart, requesting that RUNSTATS SHRLEVEL REFERENCE with SAMPLE updates RTS TOTALROWS. Also I request that even if the default sampling moves to pages that we keep available an option which is able to update TOTALROWS if it is chosen.

The related Walmart case is TS003609017. There is also a long discussion on this in the IBM internal Utility slack channel.

Needed by Date Dec 31, 2020