IBM Support

PI80168: ABEND0C4 RC10 DSNXEDWA OFFSET00E70 WHEN A SIGNIFICANT NUMBER OF CONDITIONAL ERRORS ARE RAISED FOR AN SQL STMT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND0C4 RC10 DSNXEDWA OFFSET00E70 when a significant
    number of conditional errors are raised for an SQL stmt .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 12 for z/OS users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ABEND0C4 at                                                  *
    *      DSNXGRDS . DSNXEDWA + 00E70                             *
    * when a significant number of instances                       *
    * of the condition information for an                          *
    * SQL statement were raised.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available.                         *
    ****************************************************************
    DB2 collects the diagnostic information, such as
    the statement information, the connection information, and
    the condition information, for an SQL statement.
    
    In the reported case, a significant number (more than 32767)
    of instances of the condition information were raised. That
    caused the incorrect storage referencing during the condition
    information handling, resulting in the ABEND0C4.
    
    Additional Keywords: 0C4 RC10 OFFSET0E70
    

Problem conclusion

  • DB2 has been modified to correctly handle the condition
    information for an SQL statement under the case described
    above.
    This apar also handles the connection information properly
    in the similar situation for connection information.
    
    For DB2 11 for z/OS, this problem is fixed by APAR PI80307.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI80168

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-18

  • Closed date

    2017-07-11

  • Last modified date

    2017-08-02

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

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

    PI80307 UI48706

Modules/Macros

  • DSNLTAS1 DSNXEDWA DSNLTAC1 DSNXRTSC DSNXEPAR DSNXRWND DSNNQOPM
    DSNURWBF DSNLJACC DSNXROJ1 DSNXRUWG DSNNQO
    
    ***This field was truncated.  To obtain the full apar record, please contact your local support center.***
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI48706

       UP17/07/27 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.

[{"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":"12.0","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":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2017