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 Delivered
Created by Guest
Created on Jan 5, 2017

Infosphere Classic CDC - needs to handle local time

Previous to V9.5 the time-stamp in the message represented when the Correlation Service processed the change and not the time when the application made the change. This condition of using the Classic server Correlation Service (CS) time and not the database change time.
The Classic V9.5 and higher requirement was to use the database time (e.g., IMS uses STCK's which are in UTC (GMT) format) to establish at exactly what time did a change actually occur that was being published.
There is no option to convert the time-stamps to a local time, only delimited format messages are supported for publishing to MQ.
This is the current design and for V11.3 recommend customer to submit a RFE (Request for Enhancement) to have an option in Classic to convert the UTC in V11.3 to a local time format.

  • Admin
    Eric Su
    May 21, 2021

    [IBM Update]


    Thank you for filing this requirement and for your interest in keeping our IMS/VSAM Data Replication technologies vital and successful.

    After a recent review of your request, we believe it was already addressed in one of our later releases. With that said, if our fixes did not address your request completely on the latest maintenance, we encourage you to file a new idea accompanied with any additional information that could better help us understand and prioritize your request.