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,
Post an idea
Upvote ideas that matter most to you
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.
All DB2 customers use RUNSTATS. The RUNSTATS results are used by the DB2 optimizer to determine optimal access plans. In 99.999 percent of all cases this is not a problem. However, there are some objects (tablespaces / indices) for which a RUNSTATS execution for special SQL statements (mostly dependent on value distributions) can lead to an immediate critical deterioration of access paths (and the volatile clause would also not be a solution to the problem). Today there is no easy way to fall back to the old RUNSTATS values. So the customer can be in a very critical situation! Often the customer knows these objects and takes this into account e.g. when using DSNACOXX by means of the so-called exception table. We would like a general possibility within the RUNSTATS syntax (analogous to DSNACOXX) to exclude objects from the RUNSTATS execution. E.g. by means of a new keyword EXCEPTION YES / NO (DEFAULT NO) in RUNSTATS. If the customer specifies EXCEPTION YES, it should be taken into account that no RUNSTATS is generated / executed for any object in an exception table.
Do not place IBM confidential, company confidential, or personal information into any field.