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 Apr 2, 2020

Rollback changes to both accelerators if failure occurs loading multiple accels in one load statement

We have a situation where it is important to keep the data in synch on both accelerators, so we use one statement to load both accelerators.

Real case: The data is loaded from OPERLOG logstream to shadow table every 15 minutes on two IDAA accelerators. To avoid loading duplicate data, we only load the newest rows that have been written to the logstream since the last time the load ran. To ensure this, we select the max timestamp from table in IDAA and then load the rows from the logstream that are greater than the max timestamp into IDAA. This works well unless the load to one accelerator fails and the other is successful. Then the max timestamps aren't the same on both accelerators and there is potential for either a gap or duplicates to occur next time the loads run, since we aren't guaranteed which accelerator the job will retrieve the max timestamp from.

Needed by Date Sep 1, 2020