IBM Support

PM93756: SQLCODE -303 ON FETCH BIN XML INTO HOST VARIABLE IN DISTRIBUTED ENVIRONMENT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2DRDA DB2LOB DB2XML Defect 167545 d167545
    SQLCODE -303 on fetch bin XML into host variable in distributed
    environment.
    **************************************************************
    Addition Symptoms and Keywords:
     SQLCODE303 SQLCODE -303 SQL303N SQL00303N
     SQLCODE30020 SQLCODE -30020 SQL30020N
     DSNL031I MSGDSNL031I 00D35607 RC00D35607
      DSNLZFDT DSNLZFDT0107 0107
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    *                 Specifically applications that execute on    *
    *                 a DB2 for z/OS requester system and fetch    *
    *                 LOB locators or XML data from a query on a   *
    *                 remote server.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When fetching LOB locators or XML data  *
    *                      from a remote query, an application     *
    *                      executing on DB2 for z/OS may receive   *
    *                      one of these errors:                    *
    *                      - the fetch fails with SQLCODE30020     *
    *                        (-30020) and the requester console    *
    *                        may show:                             *
    *                          DSNL031I REASON=00D35607            *
    *                            ERROR ID=DSNLZFDT0107             *
    *                      - the fetch fails with SQLCODE303       *
    *                        (-303).                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There are 3 cases in this problem:
    1. When an application executing on a DB2 for z/OS requester
       fetches LOB locators from a query on a remote server, such
       that the nullability of the target LOB locator does not
       match the nullability of the corresponding column in the
       query, DB2 incorrectly uses the application's host variable
       nullability to parse the data from the server.
       DB2 requester processing detects this mismatch, generates a
       DRDA exception with reason 00D35607, and returns
       SQLCODE30020 to the application.
    2. When an application executing on a DB2 for z/OS requester
       fetches XML data from a query on a remote server, such
       that the nullability of the target XML does not
       match the nullability of the corresponding column in the
       query, DB2 incorrectly uses the application's host variable
       nullability to parse the data from the server.
       DB2 requester processing detects this mismatch, generates a
       DRDA exception with reason 00D35607, and returns
       SQLCODE30020 to the application.
    3. When an application executing on a DB2 11 for z/OS requester
       fetches XML data from a query on a remote server, DB2
       requester processing incorrectly detects a type mismatch
       when the corresponding column is a nullable XML SQL type and
       returns SQLCODE303 to the application.
    

Problem conclusion

  • DB2 for z/OS requester processing has been corrected to fetch
    LOB locators and XML data from a remote query regardless of the
    target host variable nullablity specified by the application.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM93756

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-24

  • Closed date

    2013-09-25

  • Last modified date

    2013-11-04

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

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

    UK97915 UK97917

Modules/Macros

  • DSNLZRDT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK97915

       UP13/10/11 P F310

  • RB10 PSY UK97917

       UP13/10/11 P F310

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:
04 November 2013