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 Future consideration
Created by Guest
Created on May 12, 2021

Add Ability to Pick/Choose Which "Warnings" Are Considered Fatal VS Acceptable

We would like to be able to pick and choose which LAT warnings are acceptable vs which require additional attention. Today, all warnings will generate a return code 4; however, some warnings (like ALAA061W) will completely eliminate a tablespace from the scan, which does not meet business needs and we miss data. Other warnings (like ALAA070W) we have processes to handle, so consequently, they are of no concern to us. Right now, we have the choice to consider a scan ending with a return code of 4 or lower to be acceptable (when it may not actually be depending on what warning was encountered), or we consider a return code 4 a problem, to which people will be getting called nearly daily/nightly. This isn't feasible with the high use of this product in this shop. We would like to be able to have a way to specify which of these warning should make the job stop with a return code higher than 4 and which should not generate anything higher than a 4.

Needed by Date Jul 30, 2021