IBM Support

PK15288: OPTIMIZE BULK FETCH FOR THE ODBC API SQLEXTENDEDFETCH() WHEN RETRIEVING DATA INTO ARRAYS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Currently a DB2 ODBC application can retrieve multiple rows of
    data into an array with a single SQLExtendedFetch() call.
    This APAR will optimize DB2 ODBC's bulk fetch to use the
    multi-row FETCH statement when connected to a DB2 for z/OS
    subsystem that supports multi-row FETCH.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DB2 UDB for z/OS Version 8      *
    *                 ODBC/CLI.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: SQLExtendedFetch() still fetches only   *
    *                      one row at a time in order to retrieve  *
    *                      a rowset into application bound arrays. *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A DB2 ODBC application can retrieve multiple rows of data
    (called a rowset) simultaneously into arrays.  This method
    eliminates the overhead of extra data copies and SQLBindCol()
    calls.  However to fetch the rowset, SQLExtendedFetch() still
    retrieves only one row at a time.  After all rows in the rowset
    are fetched, SQLExtendedFetch then returns all data in the
    arrays bound by SQLBindCol().
    
    This APAR will optimize SQLExtendedFetch() by replacing the
    individual fetching of rows with DB2's multi-row fetch.
    

Problem conclusion

Temporary fix

Comments

  • The multi-row FETCH statement is only available in DB2 for
    z/OS V8 running in New Function Mode.  ODBC will only perform
    multi-row FETCH when it determines that the local DB2 server
    and the target data source are DB2 z/OS V8 servers running in
    New Function Mode.  In all other cases, the driver will
    continue to fetch one row at a time for bulk fetches.
    ×**** PE07/08/22 FIX IN ERROR. SEE APAR PK51506  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK15288

  • Reported component name

    DB2 ODBC/JDBC/S

  • Reported component ID

    5740XYR02

  • Reported release

    817

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2005-11-15

  • Closed date

    2007-06-29

  • Last modified date

    2007-11-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK26761

Modules/Macros

  •    CLI      CLIALLOC CLICVT   CLIDST   CLIERR
    CLIOPT   CLIRETR  CLISDA   CLISMP   CLISQL   CLISQLNF CLIUNI
    CLIUTL   DSN@LINF DSNAOCLI DSNAOC0O DSNAOC0R DSNAOC0U DSNAOC0V
    DSNAOC0W DSNAOC02 DSNAOC05 DSNAOC06 DSNAOC08 DSNAOC09 DSNAOC1L
    DSNAOC1V DSNAOC17 DSNAOC21 DSNAOC22 DSNAOSDK DSNAOTRC SQLTCLI
    SQLTCLQ
    

Fix information

  • Fixed component name

    DB2 ODBC/JDBC/S

  • Fixed component ID

    5740XYR02

Applicable component levels

  • R817 PSY UK26761

       UP07/07/18 P F707

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"817"}]

Document Information

Modified date:
03 March 2021