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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.