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

Q Replication for Z

Showing 60

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 ...
over 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

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 comma...
about 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

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...
over 2 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release

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

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.
about 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

V12-CERT-2017 - Support for replication of REORG DISCARD events

When a REORG discard is run on the source side in a replication relationship / event relationship we want to be able to replay this event on the target side somehow.We do not want to do this by logging the discards in the REORG, of course.One sug...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

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...

Prompt customer need to reduce prune interval

In a busy Q Rep env with many bi-di Q subs, there may lots of P2PNORECAPTURE signal insert into IBMQREP_SIGNAL control table by Q Apply program.As per design, Q Capture delete up to 10000 rows at a time for one prune interval.When the average P2P...
over 1 year ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Is a defect

IIDR STOPQ/STARTQ request should be executed in parallel beyond the queue

IIDR STOPQ/STARTQ command is isssued from customer created automated process. They are isssued for 5 queues in parallel.Customer's STARTQ will be isssued without minitoring if the previous STOPQ queue is complete through MSGASN7176I. If STOPQ pro...
over 3 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Latency Threshold Setting by Duration in ASNMON

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.
almost 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Planned for future release