Skip to Main Content
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:

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:

Status Planned for future release
Created by Guest
Created on Mar 10, 2022

Proper Error notifications for CDC capture and apply SQLCODE

We recently had issue where CDC plan on Zos Capture was bound to a wrong collection and resulted in one capture referencing the metadata of another capture.

Case TS008690724.

when this happened a +100 sqlcode was shown in the capture log but there was no indication on which table it encountered the SQLcode +100.

This made it extremely difficult to debug the issue.

The enhancement we are requesting is whenever a database request is made and upon the return of a non-zero sqlcode we would like all the SQL text to be dumped to the capture or apply logs so it becomes easy to debug the issue.

The error handling should notify in the log as much details as possible like table name, table owner or if a view is used a view name /view owner , what package made the SQL connection and which plan and collection it got invoked like SQLCA details.

We need this in every SQL returns in Zos and distributed CDC capture and the apply.

March 10th - correct Case number is TS008610884

Needed By Month
  • Guest
    Mar 10, 2022

    Update : Case TS008610884 is the case that should be referenced (NOT case TS008690724)