Skip to Main Content
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 Planned for future release
Created by Guest
Created on May 26, 2021

Improve handling of tables with structure changes in Log Analyzer Tool

The current handling of tables that have had structure changes (alters, drop/recreate) is extremely cumbersome and difficult to pro-actively manage, requiring TVFILE entries for altered tables and duplicate structures for tables that have been dropped/recreated. While the “Track Schema Changes” process can populate the TVFILE entries there is no effective way to proactively determine when that process is needed, and no good way to determine how long the TVFILE entries should remain as well as no good way to share TVFILE entries between scan processes since each scan can also update the TVFILE. There are a few options for automating the drop/recreate process, but none of them are easy to incorporate into a jobflow with other table scans.

Needed by Date Sep 23, 2021