IBM Support

PK51331: ABEND04E RC00D30014 DSNLTCM1, DSNLCMT2, ABEND0C4 RC4 DSNLBABR WITH SUBSYSTEM TERMINATION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DDFL09 DB2INACTIVE
    defects 07747_227_000 d07747_227_000 pk51331 dpk51331
    ABEND04E RC00D30014 DSNLTCM1, DSNLCMT2, ABEND0C4 RC4 DSNLBABR
    WITH SUBSYSTEM TERMINATION
    .
    04E-00D30014 DSNLTCM1:0001, 04E-00D30014 DSNLCMT2:0005,
    0C4-4 DSNLBABR+045C
    .
    DPSBLFM5 being 0.
    When DSNLQINA failed because of enclave delete failure, DB2
    freed the communication related block for other thread during
    recovery process. This caused other thread to abend during
    commit/abort processing and DB2 termination.
    ******************************************
    Additional symptoms and keywords:
      ABEND04E AB04E S004E 04E 04E-00D30014 00D30014 RC00D30014
        DSNLTCM1 DSNLTCM1:0001 0001 ABNDID0001 ABID0001 VRADC0001
        DSNLCMT2 DSNLCMT2:0005 0005 ABNDID0005 ABID0005 VRADC0005
      ABEND0C4 AB0C4 S00C4 0C4 0C4-00000004 00000004 RC00000004
        DSNLBABR DSNLBABR+045C 045C
      ABEND04E AB04E S004E 04E 04E-00D31010 00D31010 RC00D31010
        DSNLQINA DSNLQINA:0002 0002 ABNDID0002 ABID0002 VRADC0002
      DPSBLFM5 value of zero
      DSNTIPR DDF THREADS INACTIVE
      DSN6FAC CMTSTAT INACTIVE
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    *                 Specifically where DB2 is configured with    *
    *                 DDF THREADS=INACTIVE specified               *
    *                 (DSN6FAC CMTSTAT INACTIVE).                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unpredictable secondary abends, and a   *
    *                      potential DB2 abnormal termination,     *
    *                      after an 04E-00D31010 DSNLQINA:0002     *
    *                      primary abend.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    User receives initial/primary abend 04E-00D31010 DSNLQINA:0002
    but then receives secondary abends that may lead to a DB2
    subsystem termination. Secondary abend symptoms include:
    . 04E-00D30014 DSNLTCM1:0001
    . 04E-00D30014 DSNLCMT2:0005
    . 0C4-00000004 DSNLBABR+045C
    Note: The primary abend was intermittent but, when it did
      occur, the user noticed that it was always preceded by an
      abend 15F which led to application of z/OS APAR OA17703. The
      user indicated that the primary DSNLQINA abend disappeared
      after applying z/OS APAR OA17703.
    The primary abend in DSNLQINA occurred during the process of
    disassociating (inactivating) a connection from a DBAT.
    Inactivation processing is very sensitive to abends because the
    DBAT and/or connection may be left with inconsistent references
    to each others control blocks. This incomplete disassociation
    may lead to secondary abends which may also lead to a DB2
    subsystem termination.
    

Problem conclusion

  • DB2 DBAT termination processing has been changed to more
    effectively tolerate an interruption in connection / DBAT
    disassociation processing by eliminating a reference to a
    "DBAT related" DPSB control block via a set of potentially
    inconsistent "connection related" control blocks.
    Also, DB2 inactivation processing has been changed to fully
    complete the disassociation process if an 04E-00D31010
    DSNLQINA:0002 abend should happen to occur.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK51331

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-08-20

  • Closed date

    2008-01-10

  • Last modified date

    2008-02-02

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

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

    UK32886 UK32887

Modules/Macros

  • DSNLCTRC DSNLQDIS DSNLQINA
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK32886

       UP08/01/28 P F801

  • R910 PSY UK32887

       UP08/01/28 P F801

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

Document Information

Modified date:
02 February 2008