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

Alternative of Updating All or Changed Fields for SQL Update

When replication of SQL Update, only changed fields are updated now. The data consistency cannot be guaranteed if any changes are happened during the period of no replication is executed. All fields updating is required for SQL Update data replica...
about 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 1 Planned for future release

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

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

QREP Commit by Row Count

For configuration of COMMIT_COUNT, the original suggestion is to have different value for online and batch procession. Since it is not easy to define the period for online and batch (there are online and batch processes during day time), it would ...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Delivered

Enhance QREP peer-to-peer configuration

Currently most of the customer implementation of QREP is using 'unidirectional replication configuration' even the customer has need of bi-directional replication requirements. Normally applications occur on the source site only, the target tables...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Improving the performace of INITIAL LOAD

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.The function of QREP init...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Future consideration

New function when startup q-rep capture stc

When start up the appy STC, can pass the LSN by the parameter ourside JCL.
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Functionality already exists

Add control parameter when start up the q-capture

When startup the q-capture, need add a control parameter. This parameter can be used to control the q-capture do not read the log when the q-capture start up. And when the user think it's time to read log, user can using the 'F STC' to ask the a-...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Q Capture - Specify TRANS_BATCH_SZ at the SendQ level

We have q-replication from DB2 on z/OS to Native Oracle targets.Currently the TRANS_BATCH_SZ value is allowed to be specified only at the Capture level. We request for the ability to specify this at the send queue level.The reason for this request...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 0 Not under consideration

Ability to disable key dependency at queue level for non-condensed CCDs

We have q-replication configured from DB2 on z/OS to Native Oracle targets. For target non-condensed CCD tables, we request for the ability in Q-rep to disable key dependency at the Send/RecvQ level. This is to eliminate serialization of INSERTS ...
over 4 years ago in Replication: Q-Replication & Availability / Q Replication for Z 2 Delivered