PI36617: -MODIFY DDF ALIAS CANCEL COMMAND MAY NOT COMPLETE. THE ALIAS MAYREMAIN IN CANCLG STATUS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2TCPIP defect pi36617 dpi36617
  The DDF command -MODIFY DDF ALIAS(aliasname) CANCEL may not be
  able to complete. The ALIAS will stay in status CANCLG.
  MODIFY DDF ALIAS
  ***************************************************************
  Additional Symptoms and Keywords:
   MODIFY DDF ALIAS CANCEL
   DSNL087I MSGDSNL087I DSNL088I MSGDSNL088I CANCLG
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  *                 Specifically those who have enabled, or      *
  *                 plan to enable, inbound TCP/IP location      *
  *                 aliases.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: -DISPLAY DDF message pair, DSNL087I     *
  *                      and DSNL088I, continually reports a     *
  *                      STATUS of CANCLG (canceling) for a      *
  *                      canceled, dynamically defined,          *
  *                      subsetting location alias.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a -MODIFY DDF ALIAS CANCEL command is issued, DB2
  will mark any server thread (DBAT) as being canceled if
  that DBAT is associated to a client connection which
  targeted the alias.
  DB2 11 server thread processing issues TCP/IP synchronous
  receives to get the next requests from the client for the
  current in-flight unit-of-work.  Until the client sends in
  another request, the DBAT cancel request (as a result of the
  Modify DDF Alias Cancel command) is not honored leaving the
  alias status as CANCLG.
   Note: DB2 10 server thread processing issues TCP/IP
    asynchronous receives for any request from a client.  These
    asynchronous receives are terminated automatically when the
    DBAT is canceled and hence the condition does not occur in
    DB2 10.
  In DB2 10 and 11, if the current client SQL request causes a
  (hop) access to a downstream location, DB2 issues a TCP/IP
  synchronous receive against the downstream location connection
  to obtain the result of the request.  Until the downstream
  location replies, the DBAT cancel request (as a result of the
  Modify DDF Alias Cancel command) is not honored leaving the
  alias status as CANCLG.
  

Problem conclusion

• DB2 11 has been changed to drop any inbound and outbound
  connections related to a DDF server thread associated to
  a remote client whose requests target the canceled,
  dynamically defined, subsetting location alias.
  DB2 10 has been changed to drop the outbound
  connections related to a DDF server thread associated to
  a remote client whose requests target the canceled,
  dynamically defined, subsetting location alias.
  

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:

  UI27209 UI27210

Modules/Macros

•    DSNLILNR
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI27209

     UP15/05/15 P F505

• RB10 PSY UI27210

     UP15/05/15 P F505

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.