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.
Single Consistent Tool for Defining and Administering QRep Subscriptions
Consistent and comprehensive client tools are required for defining, administering and operating queue replication.Today the Replication Center and Replication Dashboard exist, and there are some functions that neither of these support and have to...
V12-CERT-2017 - Support for replication of REORG DISCARD events
When a REORG discard is run on the source side in a replication relationship / event relationship we want to be able to replay this event on the target side somehow.We do not want to do this by logging the discards in the REORG, of course.One sug...
Ability to disable key dependency at queue level for non-condensed CCDs
We have q-replication configured from DB2 on z/OS to Native Oracle targets. For target non-condensed CCD tables, we request for the ability in Q-rep to disable key dependency at the Send/RecvQ level. This is to eliminate serialization of INSERTS ...
Q Capture - Specify TRANS_BATCH_SZ at the SendQ level
We have q-replication from DB2 on z/OS to Native Oracle targets.Currently the TRANS_BATCH_SZ value is allowed to be specified only at the Capture level. We request for the ability to specify this at the send queue level.The reason for this request...
Do not place IBM confidential, company confidential, or personal information into any field.