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 Aug 20, 2018

Delete/Define operation on Vsam file needs to be logged

This RFE is for the VSAM development team.
if a vsam file is enabled for replication using LOGREPLICATE, it can be enabled for replication using Classic CDC. if such file is DELETE/DEFINE which is very common for end of day processing, the replication is broken since the source and target data gets out of sync. We would like to capture when a vsam file is involved in a DELETE/DEFINE event and it has to get logged, so CDC capture will know about it also and can send message to the syslog so that the support teams can get alerted and take appropriate action.
Its possible some user may del/define the file without knowing the file is involved in replication also.

  • Guest
    Feb 25, 2021

    We are using VSAM Remote Source and we would love to have a feature available that allows us to only capture and send updated records from an end-of-batch DELETE/DEFINE from our on-prem log reader process to our cloud-hosted remote source docker container. This would spare us from needlessly uploading 100s of GBs daily over some small connections on a private network.

  • Guest
    Feb 25, 2021

    Request to have a 'diff' function to compare old and new VSAM and send the difference to the logstream so CDC can continue capture 'changes'

  • Guest
    Mar 31, 2020

    Pre-req on IDCAMS to create the log data has yet to be delivered. We will leave this in a "Needs More Information" status until such time as we get an update from IDCAMS team that they are planning to deliver on this requirement.