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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


ADD A NEW IDEA

Replication: Q-Replication & Availability

Showing 73 of 15253

In SQL replication, do not re-execute signals that have already been executed.

In SQL replication, as in Q Capture, add a reprocess_signals to the parameters of the capture and set the default to N. Do not re-execute a signal that has already been executed if the minimum LSN is less than the last signal LSN at the start of t...

In SQL replication, do not re-execute signals that have already been executed.

In SQL replication, as in Q Capture, add a reprocess_signals to the parameters of the capture and set the default to N. Do not re-execute a signal that has already been executed if the minimum LSN is less than the last signal LSN at the start of t...

Implement more granularity processing on "CORRELID" to force more parallelism at Q Apply

We have an application with a high criticality and high workload running Q Replication in a bidirectional mode.This application uses CICS transactions, TSO Batch, Java Batch, local zWAS and distributed transactions as well.And because batch jobs c...

The customer would like to know all the related tables associated with an uncommitted Unit of Recovery (UR).

If there is an uncommitted UR (a.k.a transaction) on the Capture side, is there a method for QREP to quickly locate the tables related to the uncommitted UR?
7 months ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Future consideration

Improvement of QREP to allow replication of data generated in the Db2 LOG by the LOAD utility with SHRLEVEL NONE LOG YES.

Need: Meet the growing demand for data replication from Banco do Brasil -Scenario:- Banco do Brasil is a large user of data replication using Qrep (IIDR) + Db2 v13 for z/OS, there are thousands of tables replicated from production environments for...
8 months ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Future consideration

Possibility to execute STARTQ command with "CAPTUREUPTO" option

In high workload environments it would be very useful to let QCapture work on a STARTQ command with predefined end. Currently this can be done by a STARTQ command and after the SendQ is active a subsequent STOPQ with captureupto.But if for some re...
9 months ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Future consideration

SQLCA -904 not offload on Infosphere Q-Replication job log on z/os

QREP didn’t externalize the SQLCA error -904 on Prod DB2.. Since we dont have a SQL error Monitoring tool on one of the BU Prod db2 enabled.. So debugging the issue was difficult.. There should be some repository/documentation where this SQLCA err...
9 months ago in Replication: Q-Replication & Availability / Q Replication for Z 3 Functionality already exists

Data captured in long transactions with guaranteed delivery to destination

It is usefull because sometimes a very long transaction pass through the Capture process but can´t be delivered causing memory lack at destination. The benefit would be not losing the data transferred to the destination. One suggestion would be to...
10 months ago in Replication: Q-Replication & Availability / Q Replication for Z 2 Needs more information

Feed Q Replication with your own LOAD keywords for automatic load

Recently we had opened a case TS013850174, which could not be addressed correctly b/c it requires an enhancement. Problem was as follows. Due to an error in our change management process, target table had a unique index, which was not present at t...
about 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Provide High Availability Solution

If you currently have QCapture tasks executing on an LPAR and the LPAR or Db2 member on the LPAR crashes, there will be an outage and latency. In an environment where we are executing an n-way Db2 Datasharing group replicating to a highly availabl...
about 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration