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 Future consideration
Created by Guest
Created on Nov 10, 2020

Implement SQLCODE mapping for Federated Stored Procedures

Db2 Connect provides SQLCODE mapping when connecting to a back-end Db2 z/OS database. Federation does not offer the same feature, instead translating user-driven SQL errors to SQL1822N (SQLCODE -1822). When invoking a Db2 z/OS federated stored procedure through LUW, a different SQLCODE is returned to the calling application vs. calling the same stored procedure directly on Db2 z/OS.

Needed by Date Dec 25, 2020
  • Guest
    Nov 10, 2020

    Specific use-case is Db2 z/OS stored procedure issues a SIGNAL SQLSTATE, returning SQLCODE -438 or +438 on Db2 z/OS (and would also on Db2 LUW, if created locally). However, the federation server translates the -438 to -1822 as an unknown SQLCODE. This does not provide compatibility for the calling application.