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 Not under consideration
Components Q Replication for Z
Created by Guest
Created on Apr 3, 2019

Display of replication throughput per subscription

Today Q Apply stores detailed performance statistics on queue level. This idea raises the request to store certain Q Apply throuput statistics (like rows_processed) on subscription level. Background: Today it is very difficult / sometime impossible to identify the root cause in case Q Apply is overwelmed with workload and in case Q Apply cannot guarantee the required latency. In these situations we would like to know which tables are effected (to take correctve action on the source). The performance details we ask for could for example list the x heaviest hitters (e.g., the 10 subscriptions with the most workload). Ideally this information would be stored in a statistics table periodically or at least be written to a log file for investigation.