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
Components Serviceability
Created by Guest
Created on Dec 15, 2021

Make the Db2 Server and Client support ROWSET cursors

The Db2 server and client (Db2 Connect) today does not support ROWSET cursors.

Support of Multirow Fetch Db2 Precompiler and embedded Runtime support the fetch of multiple rows by using a single FETCH statement. Db2 ESQL enables arrays to be passed as a host variable (and as their indicators) while ESQL calls the FETCH statements as their output arguments (bind-outs) from the COBOL application. To pass the cardinality for the array FETCH statement, the Db2 Precompiler supports the “For n ROWS” clause in FETCH statement. The variable "n" in the "For n ROWS" clause can be an integer in the range 2 - 32767, a host variable declared as integer, or a short data type. If the “For n ROWS” clause is not specified, the Db2 precompiler for COBOL takes the cardinality of the array size based on the declared size of host variables that are used in the SQL. If the host variables used are of different sizes, the minimum size of all the host variables are used as the cardinality of the bulk/array. Users can check sqlca.sqlerrd(3), which indicates the number of records fetch.

The jdbc driver today support this capability following the required behavior as exist today in Db2 z/OS.

Multi-row SQL operations in JDBC applications

So, based on our journey to the cloud and digital transformation we need that feature - SQLERRD(3) maintains the number of rows returned in the fetch rowset statement like DB2 z/OS - to be available on Db2 Connect.

Needed By Month
  • Guest
    Mar 25, 2022

    Using a cursor is analogous to holding your finger on a certain line of text on a printed page. A cursor is used by an application software in Db2 to point to one or more rows in a collection of rows fetched from a table five nights at freddy's

  • Guest
    Feb 22, 2022

    Declaring Cursor -> EXEC SQL DECLARE cursor-name/cursor-variable-name SCROLL CURSOR FOR select-statement FOR FETCH ONLY END-EXEC. Opening Cursor -> EXEC SQL OPEN cursor-name/cursor-variable-name END-EXEC. Location voiture Casablanca pas cher

  • Guest
    Dec 15, 2021

    Well, unfortunately it is not a "detail in the application". And the tests executed with the Db2 Connect did not work. We worked with the IBM Db2 Support Team on that and it seems to be a gap. Thus, the guidance from support was for open this idea (RFE) in a way for improve the software and provide the same experience as provided on jdbc and on Db2 z/OS.

  • Guest
    Dec 15, 2021

    Accessing a DB2 database on the mainframe platform or on LUW should only be a detail in the application. The application should work exactly the same on both accesses, and therefore DB2 Connect has to allow this transparency.