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.
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 ...
Ability to create ASNMON Oracle Control Tables via GUI without Federated Server
We have QREP Data Replication established between DB2 Z/OS and Oracle on Linux. We are using Oracle Native Apply on the target DBMS.As per discussions and conclusions in the referenced PMR, 85301,442,000, we have 2 issues:1) We can not directly...
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...
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...
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...
Sequence Number management in a replicated DB2 system
Today sequence numbering in a DB2 subsystem that is being replicated to a secondary site needs to be managed outside of the replication support manually by the customer. Guidance has been given to use odd/even numbering on one side and the other....
ASNCLP PROMOTE to generate SQL rather than another ASNCLP Script
When using the ASNCLP PROMOTE function the output is another ASNCLP Script.We would like the PROMOTE option to generate the target SQL instead of another ASNCLP Script - applying any name changes defined in the PROMOTE command.
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...
ABC(Agriculture Bank of China) have implemented A-A based on QREP. Due to its huge number of data volume, the maintenance related to A-A is extreme complex. The more easy operation of QREP the more maintenance convenience.1. In some case, certain ...
Leverage "FOR EACH ROW ON UPDATE" functionality to maintain Peer to Peer Version Columns, instead of triggers
Current implementation of Peer to Peer Version Columns (IBMQREPVERTIME and IBMQREPVERNODE) depend on BEFORE INSERT and BEFORE UPDATE triggers to maintain transaction information for conflict_action of V (last transaction wins). The use of these tr...
Do not place IBM confidential, company confidential, or personal information into any field.