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,
Post an idea
Upvote ideas that matter most to you
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.
Document process for publication as opposed to subscription migration
The manuals document the process to migrate ALL *subscriptions* to a new Q capture task. Our scenario involved migrating single publications one-by-one (by sendq) to an existing actively used Q capture task. Please update the replication guide for...
MS SQL SERVER 2017/2019 Replication target/source support
Now is mid of 2019, but the latest MS SQL Server support is version 2016. Customer is upgrading their MS SQL Server to 2017 and above. And found the Queue Replication does not support the new 2017 server. Failed to create control table.
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 impossibl...
The Q-Replication apply programm shall be able to call the Db2 High Performance Unload (HPU) utility by the HPU stored procedure
in enterprise warehouse and OLTP areas of DB2 installations exist often very big databases with several tera bytes (often 100 of TBs) of data.
For example we have several OLTP databases with more than 20TB and tables with billion of recor...
Q-Replication Apply program shall be able to recognize if a column-organized table contains already a dictionary
the current implementation of the Q-Replication apply program for an automatic LOAD operation on column-organized target tables does not recognize if a dictionary already exist.
A column compression dictionary is used to compress data...
Customer met poor performance of spill agent issue recently. And would like to request this enhancement.The idea can be either below :1) The spill agent runs on multiple threads2) Multiple spill agents serve for one spill queue
Qrep is used to replicate data from z to distributed environment, ICBC found the Qrep apply log keep to increase and cause the difficult in operation management, so they request Qrep to enable the log split function on the apply site. they expect ...
Q Replication to allow add/remove member in P2P replication mesh
As we are migrating our DB workload to the cloud we need to have the ability to add/remove members to redefine our P2P multi-master QReplication topology to accommodate for workload growth and making data available closer to customers (application...
In a customer that has installed Q Replication, I've been working in deploy ASNMON task on z/OS side as replacement of IBM Infosphere Data Replication Dashboard tool that was deprecated. The ASN.IBMSNAP_CONDITIONS tables is used to configure the a...
After install ASNMON, ASNMON will show all history alert information in the first start, ICBC expect to use any command or parameters to suppress the history alert while start, only show the current alert information.
Do not place IBM confidential, company confidential, or personal information into any field.