PI27810: ABND=04E-00D3000E DSNLXGLM.DSNLXRSL+2734 FOR DB2 Z/OS DISTRIBUTED THREAD

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2DRDA defect pi27819 dpi27810
  A DB2 distributed thread utilizing release and connect and in
  this reported case a call to a stored procedure encounters an
  abend ABND=04E-00D3000E DSNLXGLM.DSNLXRSL+2734.
  ***************************************************************
  Additional Symptoms and Keywords:
   ABEND04E AB04E S004E 04E
    04E-00D30003E 00D30003E RC00D30003E
     DSNLXGLM.DSNLXRSL+2734 DSNLXGLM DSNLXRSL+2734 DSNLXRSL 2734
      OFFSET2734
     DSNLXGLM.DSNLXRAX      DSNLXGLM DSNLXRAX      DSNLXRAX
     DSNLXGLM.DSNLXRBF      DSNLXGLM DSNLXRBF      DSNLXRBF
     DSNLXGLM.DSNLXRCL      DSNLXGLM DSNLXRCL      DSNLXRCL
     DSNLXGLM.DSNLXRDT      DSNLXGLM DSNLXRDT      DSNLXRDT
     DSNLXGLM.DSNLXRFT      DSNLXGLM DSNLXRFT      DSNLXRFT
     DSNLXGLM.DSNLXROP      DSNLXGLM DSNLXROP      DSNLXROP
     DSNLXGLM.DSNLXRSQ      DSNLXGLM DSNLXRSQ      DSNLXRSQ
  

Local fix

• no local fix or workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Remote SQL CALL statement results       *
  *                      in ABEND04E-00D3000E                    *
  *                      LOC=DSNLXGLM.DSNLXRSL+2734              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An application running on a DB2 for z/OS requester, Site1,
  connects to a remote server, Site2.  The application calls a
  stored procedure at Site2 successfully.  The application then
  issues a RELEASE of Site2, followed by a CONNECT to Site2,
  followed by a COMMIT.  The application calls the stored
  procedure again, resulting in ABEND04E-00D3000E
  LOC=DSNLXGLM.DSNLXRSL+2734 at Site1.
   Note: This error can occur for remote SQL statements other
    than CALL.  For these cases, an ABEND04E-00D3000E may occur
    in any of these modules:
     DSNLXGLM.DSNLXMRF DSNLXGLM.DSNLXRAX DSNLXGLM.DSNLXRBF
     DSNLXGLM.DSNLXRCL DSNLXGLM.DSNLXRDT DSNLXGLM.DSNLXRFT
     DSNLXGLM.DSNLXROP DSNLXGLM.DSNLXRSQ
  The problem occurs because the CONNECT that was issued between
  the RELEASE and COMMIT caused an internal inconsistency with
  the connection state maintained by DB2.
  

Problem conclusion

• A CONNECT statement should not reverse the effects of a pending
  release state.  DB2 has been changed to maintain the pending
  release state after a CONNECT.
  

Temporary fix

Comments

APAR Information

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

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

  UI23184 UI23185

Modules/Macros

•    DSNLXRCN
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI23184

     UP14/12/04 P F412

• RB10 PSY UI23185

     UP14/12/04 P F412

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.