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.
Provide Replication Center and Replication Dashboard functionality within DSM
We would like to see the Replication Center tool functionality for IIDR Queue Replication added under the Data Server Manager(DSM) Umbrella. Today we are using Replication Center to administer and monitor our IIDR Queue Replication environment. Th...
ALTER table DATA CAPTURE NONE not detected by IIDR QREP or CDC
If 'ALTER table DATA CAPTURE NONE' is executed against a table that is actively replicating, any changes made to the source data will not be captured or replicated until â€˜ALTER table DATA CAPTURE CHANGES' is executed. This would cause the target...
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...
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...
Db2 LUW - SQL replication should optionally use TRUNCATE when performing a Full Refresh of large tables
Db2 LUW SQL Replication (10.2.1)
When you run a Full Refresh of a subscription set, the asnapply utility issues a DELETE FROM <target table> prior to the refresh of the data.
For large tables this has a significant and unnecessary overhead...
LOAD should not be restarted when Apply fails during SET INTEGRITY
When setting up Replication for a DB2 Table for the first time Apply will use a LOAD FROM Cursor to do an initial copy of the tables data. If there are constraints or generated columns defined for that table Apply will issue a SET INTEGRITY comman...
When creating new replication configurations ASNCLP checks the existence of MQ Queues, qmaps, tables, etc. When deploying to production, we need to have pre-prepared and tested the implementation scripts. However, because ASNCLP validates that the...
Transaction volume is different between business time and non-business time. Different threshold should be set for QCAPTURE_LATENCYï¼Œ QAPPLY_EELATENCYï¼Œ QAPPLY_LATENCY, e.g. 08:00 - 21:59, 22:00-07:59, etc.
For error code ASN1952E, the reason maybe ASNCLP script grammar error, QMGR setting is wrong of missed in PARM table of CAPTURE or APPLY, password of z/OS user is wrong, etc. That makes operation maintenance very hard for trouble shooting. The det...
Q Apply issue a warning after exception due to OKSQLSTATES
Using OKSQLSTATES certain error conditions can be specified which will let Q Apply document a failing operation in IBMQREP_EXCEPTIONS.Today, Q Apply does not write out a warning into the log file if an exception based on OKSQLSTATES happened.Monit...
Do not place IBM confidential, company confidential, or personal information into any field.