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 Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Nov 13, 2012

Dictionary last build date

MR0622114827 GGDB211003
  • Admin
    Janet Figone
    May 6, 2021

    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. 


    The Db2 for z/OS Team

  • Guest
    Nov 10, 2020

    I believe it would be very useful to know when a dictionary was created.

    Suppose you define a partition (or TS) and a dictionary is created day1. You have regular REORGs scheduled, but they are all coded with KEEPDICTIONARY. Some things that could happen that might require (or benefit from) a newly-defined dictionary include:

    1) Data changed via SQL or utility such that the characteristics of the data has changed enough so that a new(er) dictionary would result in better compression.

    2) Application of DB2 maintenance that might include changes to the (default) compression algorithm.

    We have a UTS PBR TS with appx. 200 partitions. I noticed that the most recent partitions (heaviest DML activity, partitioned on a key that is date-related) have the worst compression ratio of all the preceding parts. I was curious to determine the date those dictionaries were created.