IBM Support

PI15933: NO RESULT RETURN WHEN USING EXCEPT STATEMENT IN JDBC TPYE 2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • NO result returned when using the EXCEPT statement
    in a query submitted to DB2 via JDBC TYPE 2 driver.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 and 11 for z/OS users of the      *
    *                 EXCEPT statement when using the z/OS Type 2  *
    *                 IBM Data Server Driver for JDBC and SQLJ     *
    *                 (JCCT2ZOS) or the DB2 for z/OS ODBC driver.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: An incorrect result (no rows) can be    *
    *                      returned from an application that       *
    *                      contains a query that includes an       *
    *                      EXCEPT statement when using the z/OS    *
    *                      Type 2 IBM Data Server Driver for JDBC  *
    *                      and SQLJ (JCCT2ZOS) or the DB2 for z/OS *
    *                      ODBC driver.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a z/OS Type 2 IBM Data Server Driver for JDBC and SQLJ
    (JCCT2ZOS) or DB2 for z/OS ODBC driver application using an
    EXCEPT statement, the following query returns an incorrect
    result.
    
      SELECT NAME FROM SYSIBM.SYSDATABASE
      EXCEPT
      SELECT NAME FROM SYSIBM.SYSDATABASE  WHERE 1=0
    
    No rows are returned but rows are expected to be returned. The
    incorrect result occurs because DB2 is missing code to direct
    the query for limited block fetch processing since it is
    enabled.
    

Problem conclusion

  • The code in DB2 is modified to process the EXCEPT statement
    properly in applications using JCCT2ZOS or the DB2 for z/OS ODBC
    driver. This will prevent the incorrect result from being
    returned.
    
    Additional Keywords: SQLEXCEPT JCCT2ZOS DB2INCORR/K INCORROUT
                         SQLINCORR SQLINCORROUT
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI15933

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-15

  • Closed date

    2014-05-16

  • Last modified date

    2014-07-01

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

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

    UI18077 UI18078

Modules/Macros

  • DSNXRECP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI18077

       UP14/06/03 P F406 ½

  • RB10 PSY UI18078

       UP14/06/03 P F406 ½

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2014