IBM Support

PI83880: DB2 DDF THREAD ABND=04E-00D300F1 LOC=DSNLDTMG.DSNLTAC1+16D6

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2DDF DB2DRDA DB2HOP DB2TERM DB2ABTERM
    DB2 DDF thread ABND=04E-00D300F1 LOC=DSNLDTMG.DSNLTAC1+16D6
    followed by DB2 termination.
    ***************************************************************
    Additional Symptoms and Keywords:
     ABEND04E AB04E S004E 04E
      04E-00D300F1 00D300F1 RC00D300F1
       DSNLTAS1 DSNLTAS1+12D8 12D8 OFFSET12D8 (V11)
       DSNLTAC1 DSNLTAC1+16BA 16BA OFFSET16BA (V11)
                DSNLTAC1+16D6 16D6 OFFSET16D6 (V10)
     DSNV086E MSGDSNV086E 00D94001 RC00D94001
                          00E50702 RC00E50702
     ABEND04F AB04F S004F 04F
    

Local fix

  • no local workaround or fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Distributed Data Facility (DDF) users.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ABEND 04E-00D300F1 in DSNLTAC1 or                            *
    * DSNLTAS1 followed by DB2 termination                         *
    * with message DSNV086E and reason                             *
    * 00D94001 or 00E50702.                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    A remote client application, at site1, accesses a DB2 for z/OS
    server, site2, and executes SQL that refers to yet another
    remote server, at site3.
    The site3 SQL fails such that a DRDA exception condition
    related reply message is returned back to the DB2 for z/OS
    site2 server.
    Note: In the reported case, site3 was another DB2 for z/OS
    server and the SQL was related to an SQL Call statement
    where the associated Stored Procedure failed due to an
    ASUTIME expired condition.  This resulted in a 04E-00E70123
    abend (non dumping and is only reflected in LOGREC) which
    caused a DRDA AGNPRMRM reply to be returned back to site2.
    The site2 DB2 for z/OS server detects the DRDA exception
    condition related reply (from site3) but the associated DB2
    thread happened to be canceled just as it was attempting to
    issue a DSNL031I message.
    Note: In the reported case, the source of this cancel event,
    as typically the case, was due to a connection "loss"
    condition where the remote site1 client system terminates its
    connection to the site2 DB2 for z/OS server.
    The cancel event, during DSNL031I message processing, occurs in
    a timing window where the DRDA exception condition nature is
    known but the SQLCA contents have not been fully established to
    reflect the failure.
    During thread abort or deallocation processing, as a result of
    the cancel event, various DRDA command related "exit routines"
    may need to be driven to clean up resources related to the
    site2/3 connection.  Due to the incomplete SQLCA contents, a
    secondary 04E-00D300F1 abend may occur in various exit routine
    related CSECTs depending on if the site2/3 connection was via
    TCP/IP or SNA.  The secondary abend during thread abort or
    deallocation processing may lead to a DB2 for z/OS subsystem
    termination with reason 00D94001 or 00E50702.
    

Problem conclusion

  • Various DB2 DRDA command related exit routines have been
    changed to be sensitive to the potential timing of the cancel
    situation that may be involved and to therefore tolerate
    incomplete SQLCA contents.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI83880

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-30

  • Closed date

    2017-08-03

  • Last modified date

    2017-09-02

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

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

    UI49305 UI49306

Modules/Macros

  • DSNLTSL1 DSNLTEX1 DSNLTAC1 DSNLTAS1 DSNLTSC1
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI49305

       UP17/08/18 P F708 ¢

  • RB10 PSY UI49306

       UP17/08/18 P F708 ¢

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

Document Information

Modified date:
02 September 2017