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
Components Data Server Manager
Created by Guest
Created on Aug 10, 2018

Option to chose explain tables to use in DSM

We need an option to specify the schema for Explain tables within a Db2 for z/OS environment.

When running explains on Db2 for z/OS in the current version of DSM, the explain tables are tied to the current SQLID.

In our production systems the SYSADM user owns the explain tables. We do not want to give application developers access to the set current sqlid to a SYSADM account just to run explain.

We could create new explain tables but the developers would not be able to view existing access paths for packages that had been bind many years ago under the SYSADM account, as is normal for a legacy mainframe system.