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,
Post an idea
Upvote ideas that matter most to you
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.
Microseconds not getting populated for target DB2 timestamp column
"CDC built-in functions cannot retain microseconds for TIMESTAMP target data type. I have a 2 vsam fields, vsam CHAR(10) field AS 2018/08/13 (yyyy/mm/dd) and vsam CHAR(15) FIELD AS 16:19:45.094690 (hh.mm.ss.xxxxxx).I am trying to map combing both ...
Proper messaging is needed for refresh or mirror not working
When a new file is created and Augmented for replication, and a refresh or mirroring is attempted , it does not work and below message is obtained.072-053,CRTSCVS,CRTSCVS,SYS00021,,,FBSIT.DBA.V2D.CHAR 817 IEC161I FBSIT.DBA.V2D.CHARI....
Subscriptions are removed from being persistent when a target data channel comms. error is received.
==Customer is running Classic to IIDR/CDC SQL. Target SQL failed due to comms. issue in the data channel which was was considered non recoverable and dropped the sub. from being persistent. Would like the sub. to be restarted in this case.
Management console not showingÂ Classic VSAM to CDC DB2 Zos Â subscription refresh statistics
In Management console, when a Classic CDC source (VSAM table) is refreshed to the DB2 Zos target table, the refresh statistics is not displayed.In other configs, the refresh activity is clearly displayed once the "clooect statistics" is clicked.un...
Improve function for decompress of IMS type99 log using H/W component instead of MVS service
We plan to use IBM InfoSphere Data Replication for IMS for next disaster recovery system. It needs new IMS type99 log records for data replication at source system.The target system's CPU usage was dramatically increased. We would like to reduce C...
IMS, in support of HA, supports the concept of rolling maintenance where the IMS systems would be shutdown one at a time so that changes/maintenance can be applied. Once applied the system is restarted and the next IMS system is shutdown until we ...
Classic CDC/ IIDR for VSAM needs to send only needed data for Replication
Classic CDC/IIDR for Vsam capture is sending the before values for all fields in source VSAM datasets.This adds significant overhead. The capture needs to send the before and after values of the key column and before and after image of the changed...
Support IIDR reads from Secondary Volumes of Global Mirror
Support IIDR Capture reading from secondary volumes of Global Mirror.The customer uses IMS FP function for core banking systems. The customer is planning IBM InfoSphere Data Replication for IMS(IIDR) as the next DR solution instead of IMS RSR. As...
Do not place IBM confidential, company confidential, or personal information into any field.