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
Components Q Replication for Z
Created by Guest
Created on Jul 21, 2017

Leverage "FOR EACH ROW ON UPDATE" functionality to maintain Peer to Peer Version Columns, instead of triggers

Current implementation of Peer to Peer Version Columns (IBMQREPVERTIME and IBMQREPVERNODE) depend on BEFORE INSERT and BEFORE UPDATE triggers to maintain transaction information for conflict_action of V (last transaction wins). The use of these triggers results in CPU overhead, measured in internal testing at USAA at 27% avg. In DB2 CPU overhead. This overhead makes the implementation of P2P less appealing, due to implications to MLC.

However, USAA tested the use of "FOR EACH ROW ON UPDATE" functionality to maintain the IBMQREPVERTIME column, and validated that this version column can be maintained in similar fashion as the triggers do, without the associated overhead. The only barrier to implementation at this point is the lack of similar "FOR EACH ROW ON UPDATE" for constant values that can be used to represent each node in a P2P configuration.

We have submitted a separate RFE 86578 for DB2 on z/OS product to be enhanced to "Enable GENERATEd columns to apply constant ON UPDATE statements". We wanted to create this RFE for the Replication product and link them together, so they can be evaluated, prioritized and delivered in parallel.