Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 Under review
Workspace Db2 for z/OS
Created by Guest
Created on Nov 12, 2025

Support Cursor-Based Naming for Result Sets in DB2 REST Services

When a Db2 stored procedure returns multiple result sets through the REST interface, the invoke/execution JSON response content contains a part with sequentially numbered result sets ("resultSet1", "resultSet2", etc.) in the order the cursors were opened. This sequential numbering system creates ambiguity when stored procedures conditionally return varying numbers of result sets.

In order to avoid implementing complex heuristics or data inspection logic to determine which schema applies to each returned result set from a real-life multiple-resultset stored procedure, it would make this kind of stored procedure much simpler and less error prone to use from a Db2 REST caller if Db2 native REST services includes/returns cursor names for stored procedure returned resultset(s) as part of the invoke/execution response content.

To be clear, we are not asking for Db2 to present this information in its “discover service details” processing.

Needed By Not sure -- Just thought it was cool