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 Future consideration
Created by Guest
Created on Jul 2, 2020

Replication support for HPSS feature

Technical Problem

Assume there is a partitioned tablespace and some parts are archived via HPSS. Therefore, there are archived and non-archived partitions.

Db2 transparent archive is not the case in this scenario. There is only one table with PBR Tablespace.

In V5, we do HPSS for that table. Some parts are archived. Then when we enable replication, the updates coming to non-archived partitions in Db2, will be replicated via CDC to IDAA

In V7, this does not work with CDC or Insync. Simply we can not enable replication after the archive process. So we can not replicate incoming updates for non-archived partitions to IDAA.

Needed by Date Dec 31, 2020
  • Guest
    Jul 6, 2020

    it a missing feature we must have. Thanks