Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 (

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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Not under consideration
Created by Guest
Created on Apr 17, 2024


At the moment only a RUNSTATS TABLESPACE with INDEX (ALL) is possible. When using DSNACCOX suggestions for a RUNSTATS may be generated only for one or few partitions of a PBR-TS.

I therefore suggest a additional parameter (e.g. NPI YES/NO) to constraint the RUNSTATS only occur on partitioned indexes and the partition defined in the RUNSTATS TABLESPACE.

The improvement could also be implemented with all inline statistics (REORG, etc.)

Needed By Yesterday (Let's go already!)
  • Admin
    Janet Figone
    May 21, 2024

    Dear Florian, Thank you for submitting this enhancement request. The Db2 utilities team reviewed it provided the following feedback for you:

    Generally speaking, Db2 Optimizer prefers to see consistent statistics between the table space and its indexes for access path selection, that's why predominately almost all external users who run RUNSTATS TABLESPACE today would also specify INDEX(ALL) to re-gather all related statistics as a complete set, even if the target is only a subset of data partitions. We are not sure the exact reason why you would want to skip over the NPIs, but that can be achieved by either specifying the individual index names under the INDEX keyword, or break up the RUNSTATS TABLESPACE and RUNSTATS INDEX into multiple jobs. Also, if you are running RUNSTATS TABLESPACE LIST INDEX(ALL) with a LISTDEF PARTLEVEL, the NPI statistics would only be gathered once on the very last partition/list item execution to avoid regathering the NPI statistics multiple times for each intermediate data partition being targeted.

    We appreciate your input to the Db2 Utilities 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 utilities.


    Db2 Utilities Team