IBM Support

PM63756: ABEND0C4 RC00000038 AT DSNXEDP +9290 WHEN DB2 TRACE CLASS 29 TRACES IFCID316 IFCID318 IFCID400 IFCID401 ACTIVATED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following abends occurred when DB2 trace class 29 traces
    IFCID316 & IFCID318  or  IFCID400 & IFCID401  are active
    and a valid SQL error occurred at certain points of the
    SQL statement's execution:
      ABEND0C4 RC00000038 at DSNXEDP +920
      ABEND0C4 RC00000038 at DSNXERD +1F18
      ABEND0C4 RC00000011 at DSNXEBR +3F74
      ABEND04E RC00E3000A at DSNXERD +2E44
    The SQL error was returned to the user application, and
    the abends occurred during subsequent SQL execution in the same
    application or different application using the same DB2
    connection or thread.
    .
    Other abends are also possible.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users of DB2 monitor trace class 29  *
    *                 or traces IFCID316 IFCID318. Also, DB2 10    *
    *                 users of traces IFCID400 IFCID401.           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *                      ABEND0C4 RC38 AT DSNXEDP OFFSET9290 or  *
    *                      ABEND0C4 RC04 AT DSNXEBR OFFSET3F7A or  *
    *                      ABEND0C4 RC38 AT DSNXERD OFFSET1F18     *
    *                      and other abends are possible, when     *
    *                        DB2 trace class 29 is active,         *
    *                                  or                          *
    *                        IFCID316/IFCID318 are active,         *
    *                                  or                          *
    *                        IFCID400/IFCID401 are active.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When DB2 monitor trace class 29, traces IFCID316 & IFCID318 ,or
    traces IFCID400 & IFCID401  are active and a valid SQL error
    occurred at certain points of the SQL statement's execution,
    due to DB2 internal error flow processing DB2 did not reset
    an internal pointer to temporary trace storage that is used
    with these specific class 29 traces.  This DB2 temporary trace
    storage is used if trace IFCID58 is not also explicitly
    activated when these class 29 traces are active.
    .
    Upon a subsequent SQL stmt execution in the same application or
    a different application using the same DB2 connection or
    thread, DB2 reused the residual internal pointer to that same
    temporary trace storage which was not intended for this
    subsequent SQL statement. This resulted in a DB2 storage
    overlay and the reported abends. Other DB2 abends are also
    possible.
    .
    The DB2 storage overlay does *not* occur if the SQL statement
    runs successfully and no -SQLCODE is returned by DB2 when
    the class 29 traces are active.
    The storage overlay also does not occur if trace IFCID58 is
    also active when class 29 traces IFCID316/IFCID318 or IFCID400/
    IFCID401 are active.
    

Problem conclusion

  • DB2 has been modified to ensure that when an SQL error occurs
    for an SQL statement, the internal ptr to the DB2 temporary
    trace storage is reset so that same temp trace storage is not
    reused for a subsequent SQL stmt on the same DB2 thread/
    connection.
    .
    Additional keywords: SMCOVERLAY DB2OVRLAY/K AB0C4
                         AB0C4 RC00000004 RC00000038
    

Temporary fix

  • AM63756
    

Comments

APAR Information

  • APAR number

    PM63756

  • 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

    2012-05-02

  • Closed date

    2012-07-16

  • Last modified date

    2012-08-08

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

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

    UK80337 UK80338

Modules/Macros

  • DSNXERT
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK80337

       UP12/08/01 P F207

  • R910 PSY UK80338

       UP12/08/01 P F207

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:
08 August 2012