IBM Support

PI53948: ABEND 04E 00D300FD LOC=DSNLXGLM.DSNLXCM2+0778

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND 04E 00D300FD LOC=DSNLXGLM.DSNLXCM2+0778 during commit
    processing when DB2 finds the connection is already gone.
    This case was reported in an IDAA environment
    
    ABEND 04E 00D300FD LOC=DSNLXGLM.DSNLXCM2+074E
    ***************************************************************
    Additional Symptoms and Keywords:
     IDAAV4R1/K IDAAV5R1/K
     ABEND04E AB04E S004E 04E
      04E-00D300FD 00D300FD RC00D300FD
       DSNLXCM2 DSNLXCM2+0778 0778 OFFSET0778
       DSNLXCM2 DSNLXCM2+074E 074E OFFSET074E
     Defect 181810 d181810
    

Local fix

  • no local fix/workaround
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users of the IBM Data Analytics      *
    *                 Accelerator (IDAA).                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR addresses two unrelated       *
    *                      symptoms:                               *
    *                      1. ABEND04E-00D300FD at                 *
    *                         LOC=DSNLXCM2+0778 may occur during   *
    *                         commit processing after statements   *
    *                         have been offloaded.                 *
    *                      2. INSERT, UPDATE, or DELETE            *
    *                         statements on an accelerator-only    *
    *                         table complete with SQLCODE 0,       *
    *                         however subsequent queries show no   *
    *                         changes resulting from those         *
    *                         statements.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following two unrelated conditions are reported:
    1. An application offloads SQL statements to an accelerator
       followed by a commit.  During commit, DB2 will disconnect
       from accelerator locations where all offloaded statements are
       finished.  However, the connection to the accelerator may
       have already terminated, possibly due to a prior network
       error.  If the accelerator connection no longer exists, a
       disconnect during commit results in ABEND04E-00D300FD
       LOC=DSNLXCM2+0778.
    2. An application connects to a DB2 for z/OS server and
       executes SQL resulting in changes to a DB2 table.  The
       application then offloads an INSERT, UPDATE, or DELETE
       statement to an accelerator-only table.  The offloaded
       statement correctly completes with SQLCODE -919.  This error
       happens because updates occurred on both the DB2 server and
       the accelerator within the same transaction, which IDAA does
       not support.  The application issues a ROLLBACK as required
       for SQLCODE -919.  DB2, in error, did not forward the
       ROLLBACK to the accelerator, resulting in an inconsistent
       state on the IDAA server.  Subsequent offloaded INSERT,
       UPDATE, or DELETE statements complete with SQLCODE 0, but
       queries show that no changes resulted from executing those
       statements.
    

Problem conclusion

  • DB2 has been changed as follows:
    1. During commit processing, DB2 will check that the IDAA
       connection exists before disconnecting.
    2. DB2 will flow ROLLBACK requests to the accelerator as
       needed.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI53948

  • 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

    2015-12-10

  • Closed date

    2016-01-20

  • Last modified date

    2016-03-02

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

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

    UI34611 UI34612

Modules/Macros

  • DSNLTDT1 DSNLTPUN DSNLXCM2
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI34611

       UP16/02/05 P F602 Ž

  • RB10 PSY UI34612

       UP16/02/05 P F602 Ž

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 March 2016