Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

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.