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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


ADD A NEW IDEA

FILTER BY CATEGORY

Replication: Q-Replication & Availability

Showing 60

Request for re-try / reconnect mechanism

We'd like to request Replication to have re-try / reconnect mechanism even without MQ multiple instances. Because currently it doesn’t support MQ multiple instances, we can use SLB, but if it has no re-connect, we can do nothing.

Request for supporting MQ automatic client reconnect

As we know, IBM MQ supports multi-instance configuration and automatic client reconnect since version 7.0.1. Recently we found the latest Q-Relication (11.4.0) even not support such a basic function( automatic client reconnect with multi-instance ...

Request for supporting MQ automatic client reconnect

As we know, IBM MQ supports multi-instance configuration and automatic client reconnect since version 7.0.1. Recently we found the latest Q-Relication (11.4.0) even not support such a basic function( automatic client reconnect with multi-instance ...

Request for supporting MQ automatic client reconnect

As we know, IBM MQ supports multi-instance configuration and automatic client reconnect since version 7.0.1. Recently we found the latest Q-Relication (11.4.0) even not support such a basic function( automatic client reconnect with multi-instance ...

Add ability to have multiple Q-replication targets on Db2wh

Currently on Db2wh, there is no ability to add multiple targets for Q-Replication. Please consider adding that idea as we have business case to implement such solution

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...
9 months ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Future consideration

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.

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 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

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...
almost 2 years 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., non...
almost 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration