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:



Replication: IMS / VSAM

Showing 106

Documentation of raw data format in Classic CDC MQ publishing.

This is not functional requirement, but documentation requirement. it seems that Classic CDC MQ publishing have a capability to publish data format by using PUBBINASIS=TRUE. I've found this function in developerWorks.
over 2 years ago in Replication: IMS / VSAM  / Classic Change Data Capture 0 Future consideration

High availability for IMS CDC in a SYSPLEX environment

We are currently implementing CDC for IMS in our Production environment. This consists of 2 IMS v15.2 systems running on 2 different LPAR's, in a SYSPLEX. The OS on both are currently z/OS 2.3. CDC for IMS runs on 1 LPAR, replicating the LOGS of b...
10 months ago in Replication: IMS / VSAM  / Classic Change Data Capture 2 Future consideration

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 replicat...
over 3 years ago in Replication: IMS / VSAM 3 Future consideration

Needs a clean-up solution when open thread is active and there is an IMS outage

Please refer to the PMR:01622,69G,760.-----------------------------My customer does not want to restart the apply server when recovering the IMS failure.This is because the replication stop time expands and the data reflection on the target is del...
over 4 years ago in Replication: IMS / VSAM 1 Not under consideration

Restart Latency event within IIDR EIF

Add event to filter and trigger on Restart Latency.
over 1 year ago in Replication: IMS / VSAM  / Data Replication for VSAM for z/OS 0 Delivered

NMI enhancement

add Restart Latency value to the NMI data captured in the target server.
over 1 year ago in Replication: IMS / VSAM  / Data Replication for VSAM for z/OS 0 Delivered

Log updates replicated by CFC1 writer tasks to the target file's logreplicate logstream

If an application owner asks if you can verify when or if a specific update was replicated to the target site, there isn't any diagnostic information available to confirm if/when the update was replicated, since the updates applied via a CFC1 writ...
about 2 years ago in Replication: IMS / VSAM  / Data Replication for VSAM for z/OS 1 Delivered

Exit with non-zero return code or abend after a subroutine or other abend

IMS CDC terminates with a zero return code after one of its IMS subroutines abends -- 'playing havoc' with customer replication processes and schedules. IBM Cases TS002591910 and TS002591963 detail the troubling, non-mainframe behavior of IMS...
about 2 years ago in Replication: IMS / VSAM 1 Delivered

Write type 99 records to a different log stream

The Type 99 records are not needed for IMS database integrity andtheir processing consumes a large amount of I/O bandwidth on thecritical OLDS log stream. It would be useful to split this I/O to a differentlog stream (along with copies of the nece...
over 3 years ago in Replication: IMS / VSAM 1 Not under consideration

Create SQL reference manual for InfoSphere Classic Federation Server for z/OS

My customer is developing an application that issues SQL to DB2 using the CLASSIC FEDERATION.The available SQL was answered with DB2 V4 equivalent on the PMR, but LOCK was not available.Application development is delayed and the customer is strong...
over 3 years ago in Replication: IMS / VSAM 0 Future consideration