Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Delivered
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
  • Guest
    May 8, 2023

    For those implementing this PTF, a table (ALA_WARNING_ACCEPTANCE) needs to be created to use the functionality. There appears to be no hold doc for this PTF to inform you of this.

  • Admin
    Chris Pomasl
    Apr 19, 2023

    Thank you for the idea. It has been implemented via PTF UI91341