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.
Adding of a new apply parameter DBLOAD_OPTIONS in order to influence an automatic load performed by the Q-Replication apply program on column-organized tables.
A column compression dictionary is used to compress data in a column of a column-organized table. When you load data into a column-organized table, the first phase is the analyze phase, which is unique to column-organized tables.The analyze phase ...
Replicating clone tables from a source data store and tables which have a clone table defined
As per IDR 11.4, support is not provided either for replicating source clone tables or for replicating tables which have a clone table defined. We need to be able to replicate source tables involved in clone relationships.
support for CHG_UPD_TO_DEL_INS=Y in Q-replication z/OS
we are on DB2 z/OS V12R1M509 and are migrating our applications from SQL-replication to Q-replication. we have multiple applications which use Non-Condensed, Non-complete CCD targets and are built around using IBMSNAP_REGISTER CHG_UPD_TO_DEL_INS=Y...
Heartbeat messages are not available in EP if using delimited format
1. As far as including schema changes in EP messages â€“ at this time they don't have a pressing need so I would say you don't have to worry about that. However, they do want/need to see heartbeat messages. The manual says heartbeat messages are n...
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...
Qrep support Removing a column from the replication key
Currently, adding a column to the replication key is supported today by Q Replication, even for Oracle targets. But, Removing a column from the replication key is not supported today. From customer operation, they think should be allowed to change...
Currently MRI (Multiple Row Insert) function is said to be supported on DB2 for LUW after 10.5.0.7, but actually NOT. Without this function, QREP may not meet the performance requirements of some applications , such as PBoC TIPS2. https://www.ibm....
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 s...
QCapture should recognize column with FIELDPROC at CAPSTART time
QCapture should check if the source table has FIELDPROC in any of its column when it process the CAPSTARTsignal. Today QCapture checks if the source tables have any FIELDPROC at start or reinit time and keeps this information in memory. If a new t...
QRep Delete/Insert Record in CCD table for Updates of Replication Key
ICBC use CCD table to update its application DB. There is only one record of Update in CCD table for updates of replication key in Qrep. ICBC cannot remove the origin record with the information in the updated record. Data consistency cannot be gu...
Do not place IBM confidential, company confidential, or personal information into any field.