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 Future consideration
Workspace Db2
Created by Guest
Created on Jul 15, 2021

Call stored procedure from Cobol in SP

I have a Client that previously used this IBM.Data.DB2.iSeries connector, to execute local WEB sessions, they decided to go to the Azure Cloud, the only thing they changed to the SP was the IBM.Data.DB2.Core Connector, with its corresponding change in the connection string, the basic SP without Store procedure, works without novelty only those with Store procedure, indicates error -0751, and the solution is to modify the storage procedure, this storage procedure is used by many programs locally , they want to bring legancy applications like cobol and rpg to app service, but they keep making calls to legancy programs.

Which would be the best for the client, it was already indicated that the IBM.Data.DB2.iSeries connector was replaced by IBM.Data.DB2.Core and IBM.Entity.Framework.Core, the latter had not been added.

Needed By Yesterday (Let's go already!)