Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


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
    Reply
    |
    Mar 10, 2022

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