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:



Replication: Q-Replication & Availability

Showing 67

Encrypted Emails from ASNMON on Z

In our replication environment ASNMON is running on Z to monitor Q Replication processes on a significant number of Z systems. In case ASNMON records an exception, ASNMON sends emails to admin accounts. The mail server team generally requires encr...

Gracefully handle table failures & send email alert

When a table fails due to structure or availability changes, the replication set should instead set the failed table to inactive instead of crashing capture. It should also send an email notification to alert of the issue.

support for CHG_UPD_TO_DEL_INS=Y in Q-replication z/OS

we are on DB2 z/OS V12R1M509 and are migrating our applications from SQL-replication to Q-replication. we have multiple applications which use Non-Condensed, Non-complete CCD targets and are built around using IBMSNAP_REGISTER CHG_UPD_TO_DEL_INS=Y...
2 months ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

Add an ability to start a q subscription via MODIFY on the Capture started task

Currently Q Capture subscriptions can be interacted with either via MODIFY command invoked on a Q Capture started task, or SQL insert statements executed on table IBMQREP_SIGNAL. For many customers, executing a MODIFY command to perform an action ...
4 months ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

Add CAPTUREUPTO as Q Capture startup parameter

We need an emergency mechanism to control the capturing of a limited and dedicated amount of time. Today, Q Capture can be stopped when a dedicated timestamp is reached using CAPSTOP CAPTUREUPTO=<ts>. But that is not useful when Capture is d...

For ASNMON update ASNMAIL EXIT with certain industry standard capabilities

Due to new internal infrastructure requirements, and the loss of the Q-REP dashboard, we need to be able to send email alerts via ASNMON. In order to do this, the ASNMAIL Exit must be enhanced to accommodate certain features which are considered ...
about 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Delivered

Removed forced Requirement to force Replication Center to only run wit IBM JDK/JRE

Citigroup has a rule that only JDK/JRE that are supported by Citi are allowed to be used on all products that are packaged for general users. Currently the internal packaging team at Citi striped the IBM JDK/JRE from a Data Server Client 11.1.2. A...
about 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Future consideration

Ignore log records for a dedicated subscription in IGNORETRANS

In very rare cases Db2 cannot provide log records for Q Capture, e.g. in case of a version mismatch, a compression dictionary error, etc. Removing the subscription and reloading the target is a practical approach. But in some situations (e.g., no...
about 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

SQLREP Capture and Apply

#1. SQLREP Capture Program problemThere is no way to replay a single registration from DB2 log. Currently it is all or nothing when it comes to starting Capture from a synch point. This is a problem because customers want to have the ability for ...
over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Enhancement to add bidirectional Q subscription in one Db2 Server

We have the need to replicate data between two applications which are hosted in the same Db2.The challange was to exchange the data asynchron. The applications do not want to be disturbed if there is a downtime or problem at the other application ...
over 1 year ago in Replication: Q-Replication & Availability 0 Not under consideration