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

Replication: Q-Replication & Availability

Showing 65

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

ASNCLP Error Message Enhancement

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

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

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

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

Add CAPTUREUPTO as Q Capture startup parameter

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

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

DR4A V1.2 Sequence not replicated

After insert on capture side on table with autonumber column, data is inserted, but sequence is not replicated on apply side. You can follow the following steps to recreate the scenario. CREATE LARGE TABLESPACE "TSD_DBA_TEST" IN DATABASE PARTITION...

ASNCLP to support a VALIDATE(NO) option

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