PI47884: REMOTE CLIENT ENVIRONMENT NOT AWARE OF DB2 11 CANCEL CONDITIONS

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• DB2DDF DB2TCPIP defect pi47884 dpi47884
  Remote client environment not aware of DB2 11 cancel conditions.
  ***************************************************************
  Additional Symptoms and Keywords:
   Error Code -30108 ErrorCode30108
   Error Code -1224  ErrorCode1224
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unpredictable symptoms may occur as a   *
  *                      result of remote client application     *
  *                      environments that may not be aware of   *
  *                      DB2 11 for z/OS cancel related events.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a DB2 for z/OS server thread (DBAT) is canceled, via
  various cancel sources such as the Cancel Thread command or an
  Idle Thread Time-out condition, DB2 will attempt to send an
  error related reply (DRDA AGNPRMRM) to the remote client
  environment in order to acknowledge and identify the cancel
  event.  The remote client environment may return this
  information to the associated client application and/or use
  this information to help determined its subsequent processing
  behavior.  This may be especially true for Work Load Balancing
  (WLB) enabled clients where the information may be used to
  determine if application SQL work can be re-routed to other
  members of a DB2 for z/OS data sharing group.
  DB2 11 for z/OS implemented a TCP/IP connection related
  performance improvement that is achieved by using a Synchronous
  Receive socket call operation while a remote application is
  actively processing in a transaction.  As a result, when a
  DB2 11 for z/OS cancel event occurs, DB2 must first issue a
  TCP/IP Drop against the connection in order to break the DBAT
  out of its synchronous (blocking) receive operation.  The fact
  that the inbound connection had to be dropped prevents DB2 from
  returning the error related reply (DRDA AGNPRMRM) information
  to the remote client that identifies the cancel event.  The
  remote client environment may therefore be unable to handle the
  condition as seamlessly as it could relative to prior versions
  of DB2 for z/OS.
  Remote client environment symptoms may be unpredictable but one
  known symptom is a client driver error code -30108, as opposed
  to error code -1224 that was received relative to prior
  versions of DB2 for z/OS.
  

Problem conclusion

Temporary fix

Comments

• DB2 11 for z/OS has been changed to utilize a Synchronous
  Receive socket operation that can be influenced by a time-out
  interval.
  If the synchronous receive time-out period expired, DB2 will
  re-issue the receive asynchronously.  This allows remote OLTP
  related application environments to continue benefiting from
  the Synchronous receive operation, but also allows DB2 cancel
  events to be acknowledged without the need to drive a TCP/IP
  Drop operation on the inbound connection.
  ×**** PE16/02/25 FIX IN ERROR. SEE APAR PI58082  FOR DESCRIPTION
  

APAR Information

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

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

  UI31908

Modules/Macros

• DSNLAGNT DSNLAGNX DSNLCCLO DSNLCITR DSNLIENO
  DSNLILNR DSNLIRCA DSNLIRTR DSNLTRAG
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI31908

     UP15/10/24 P F510

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.