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:



Q Replication for Z

Showing 59

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 ...
about 1 month ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Under review

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 ...

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...
10 months 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

Q Replication to Kafka Targets

Kafka evolves as a platform for real time data streaming, analytics, and event processing. For enterprise customers the challenge is to let data originating on IBM z flow to Kafka. Popular options are Kafka APIs, MQ, data replication. Only data re...
over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 3 Not under consideration

Prompt customer need to reduce prune interval

In a busy Q Rep env with many bi-di Q subs, there may lots of P2PNORECAPTURE signal insert into IBMQREP_SIGNAL control table by Q Apply program.As per design, Q Capture delete up to 10000 rows at a time for one prune interval.When the average P2P...
over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Is a defect

Reduce the number of Db2 threads when replicating table with XML column

When a table with a XML column is replicated, we observed a high number of SMF Db2 accounting records, one for each row that a have a XML column. The records are due to Db2 threads created by the replication process. As the Db2 SMF records are g...
over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

ASNCLP to support a VALIDATE(NO) option

When creating new replication configurations ASNCLP checks the existence of MQ Queues, qmaps, tables, etc. When deploying to production, we need to have pre-prepared and tested the implementation scripts. However, because ASNCLP validates that the...
almost 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release