PM81500: IMPROPER SQLERROR SQLCODE PROCESSING RESULTS IN INCORROUT FOR SEQUENTIAL CASE, OR LOOP IN DSNXPSRD FOR PARALLELISM CASE

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When SQL statement gets SQLERROR (e.g. SQLCODE330), an improper
    SQLCA processing may happen, which results in incorrout for
    sequential case, or parent loop in DSNXPSRD for //ism case.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users          *
    *                 of queries containing predicates.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Improper SQL error processing can occur *
    *                      for a query involving predicates when   *
    *                      the query is being executed             *
    *                      sequentially.  If the query is executed *
    *                      with parallelism, a loop can occur.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Improper SQL error processing can occur for a query involving
    predicates.
    
    When DB2 is processing a query with predicates and an SQLCODE
    -330 (SQLCODE330) or -332 (SQLCODE332) error is expected, the
    error message may not be properly formatted when the query is
    running sequentially.  Additionally, if the query is executed
    with parallelism, a loop can occur.
    
    There are many reasons that DB2 will issue an SQLCODE -330 or
    -332.  One scenario is when converting a UNICODE string into an
    EBCDIC string and the resulting string is not a valid EBCDIC
    string.  In this case, DB2 is supposed to issue an SQLCODE.
    But, due to the processing error, no SQLCODE is formatted for
    certain cases.
    

Problem conclusion

  • The code in DB2 has been modified to process SQL errors
    properly so that the error will be externalized as expected.
    So, the correct SQL code will be issued which will prevent the
    incorrect result from being returned for the sequential case or
    the looping condition for the parallel case.
    
    Additional Keywords: SQLCODE330 SQLCODE332
                         SQLINCORR SQLINCORROUT INCORROUT
                         DB2INCORR/K DB2PARALL/K
                         PARALLELISM SQLPARALLELISM
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM81500

  • 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

    2013-01-28

  • Closed date

    2013-06-19

  • Last modified date

    2013-08-02

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

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

    UK95252 UK95253

Modules/Macros

  •    DSNXRFC  DSNXRFC9
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK95252

       UP13/07/09 P F307

  • R910 PSY UK95253

       UP13/07/09 P F307

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM81500

Modified date:

2013-08-02

Translate my page

Machine Translation

Content navigation