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 (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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 https://ideas.ibm.com


Status Planned for future release
Created by Guest
Created on Dec 7, 2020

Standardize and allow LISTDEF PARTEVEL syntax for MODIFY STATISTICS utility

Currently MODIFY STATISTICS utility does not support LISTDEF with PARTLEVEL and throws an error like in example:

LISTDEF DB2RK

INCLUDE TABLESPACE DS0HUZX.S0HU37P PARTLEVEL(20)

TEMPLATE COPYIC DSN(&SS..ICR.&DB..&TS..P&PA..&UQ.)

TEMPLATE RECSYS DSN(&SS..SRE.&DB..&TS..&UQ.)

DISP(NEW,DELETE,DELETE)

REORG TABLESPACE LIST DB2RK

LOG NO COPYDDN(COPYIC) SORTDATA NOSYSREC

DEADLINE CURRENT TIMESTAMP + 4 HOURS RETRY 6

RETRY_DELAY 120 MAXRO 25 LONGLOG DRAIN

DRAIN_WAIT 25 DELAY 90 TIMEOUT TERM

SHRLEVEL CHANGE

UNLDDN RECSYS SORTDEVT SYSDA KEEPDICTIONARY

RUNSTATS TABLESPACE LIST DB2RK TABLE(ALL)

SHRLEVEL CHANGE UPDATE ALL HISTORY ALL

STATCLGMEMSRT 4096

SORTDEVT SYSDA SORTNUM 16

MODIFY RECOVERY LIST DB2RK DELETE AGE 20

MODIFY STATISTICS LIST DB2RK DELETE ALL AGE 60

RC=08 and the message is:

DSNU050I 191 14:15:55.98 DSNUGUTC - MODIFY STATISTICS LIST DB2RK DELETE ALL AGE 60

DSNU1003I 191 14:15:55.99 DSNUGULM - INVALID LIST FOR MODIFY STATISTICS UTILITY

DSNU012I 191 14:15:56.00 DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8

There is a need for various reasons for this utility to be standardized with other utilities to operate on partition level. Firstly, as per example above, it is impossible to execute standardized housekeeping syntax to run all required utilities for given partition in one execution. Combined as above is rendering an error.

Most important is fact, that vast majority and the biggest of the statistics history collection tables have and recognize partition of the object. There is a lot of applications that use the partitions over time and then switch to next partition per business period for example, business unit, time etc. As result, it is very common situation when some partitions are stable and do not need stats collection, while other parts needs to get runstats running every day as data changes, grows in it etc. With current design and lack of functionality, those stats only ever grow as it is not possible to trim old stats, for example month old for only currently used partition, not impacting historical stats collected for other partitions. Even though as mentioned, majority of biggest (column related) stats history tables are partion aware. Among others, for this reason those tables grow like crazy while they do not need to.

Needed by Date Jan 20, 2021