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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Components Data Server Manager
Created by Guest
Created on May 1, 2017

Data Server Manager Repository Schema Names - there are too many

When setting up the Repository Database to support Query Tuning in Data Server Manager, there are 16 schema qualifiers. This makes it a nightmare setting up security for the ID that is attached to the repository. I would like this to be changed. I see no need to have this many qualifiers, complicating the initial authorization requests and subsequent changes to the product. It would nice to have one qualifier that could be setup with the update authorization that would cover all current and future table definitions. If the reason for the high number of schemas is to identify the function, then this is not a good reason. The table name should be used for that. It should be set up the same as Data Studio, with one qualifier, DB2OSC, that makes it easy to tie all Data Studio tables and packages to a single product.
  • Guest
    May 20, 2021

    Hello, thank you for your Idea. We will not be implementing this enhancement in Data Server Manager.

    However, when building the new Db2 Data Management Console, we enhanced the repository design to address the issue. LUW customers can use DMC today.

    We will consider this request for future z/OS tooling for DBAs.