IY98605: IN 2PC PROCESSING, DB2 CONNECT DOESN'T FLOW THE CORRECT DRDA DATA STREAM TO A DB2/390 SERVER DURING A DISCONNECT PROCESSING.

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• During a 2 Phase Commit, if a DB2 client drops the connection
  with DB2 zOS/390 server, the DB2 Connect gateway may not send
  the proper DRDA data stream before disconnecting from the host
  causing an abrupt closing of the TCP/IP socket. This abrupt
  closing of the TCP/IP socket causes many soft cancels on the zOS
  side, which in turn causes the CSA to become full.
  
  Other symptoms observed, of this abrupt closing is an abend
  on the host machine with the a similer msg as below:
  
  ABEND REASON CODE: 00E50013
  RECOVERY ROUTINE CSECT NAME: DSNLFRCV
  SUBFUNCTION: DTM DSNLTDRB
  

Local fix

Problem summary

• Users effected: ALL
  Problem Description: IN 2PC PROCESSING, DB2 CONNECT DOESN'T FLOW
  THE CORRECT DRDA DATA STREAM TO A DB2/390 SERVER DURING A
  DISCONNECT PROCESSING.
  Problem Summary: IN 2PC PROCESSING, DB2 CONNECT DOESN'T FLOW
  THE CORRECT DRDA DATA STREAM TO A DB2/390 SERVER DURING A
  DISCONNECT PROCESSING.
  Module : engn_sqjr
  

Problem conclusion

• First fixed in DB2 UDB Version 8 fixpak 16
  

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:

  IY98609

Modules/Macros

• eng_sqjr
  

Fix information

• Fixed component name

  DB2 CEE AIX

• Fixed component ID

  5765F3000

Applicable component levels

• R820 PSY

     UP