A fix is available
APAR status
Closed as program error.
Error description
Dynamic alias reamins in CANCLG state after -MODIFY DDF ALIAS(aliasname) CANCEL command. Additional keywords and symptoms: *********************************** DB2DDF DDF MODIFY ALIAS CANCLG
Local fix
A DDF recycle will remove the CANCLG state for the dynamic alias.
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * * Specifically those that utilize the DB2 * * dynamic location alias support. * **************************************************************** * PROBLEM DESCRIPTION: A CANCELed alias remains in CANCLG * * state or a STOPped alias remains in * * STOPG state. * **************************************************************** * RECOMMENDATION: * **************************************************************** During the processing to either cancel or stop a dynamic location alias, DB2 issues a Close of the TCP/IP socket for any inactive client connection that utilized the location alias in its connection to DB2. The intent is that DB2 will be notified to handle the termination of the client connection. However, a Close of the socket did not cause DB2 to be notified of a connection termination. This causes the location alias (being canceled or stopped) to remain in a CANCeLinG or STOPpinG state. Since DB2 cannot fully terminate the client connections which have used the location alias, a canceled or stopped location alias will remain in CANCLG or STOPG state.
Problem conclusion
To correctly handle the canceling or stopping of a dynamic location alias, DB2 has been changed to utilize the Cancel socket call for any inactive connection's pending TCP/IP asynchronous communications. This causes DB2 to be notified by TCP/IP to terminate the client connection. Once all inactive connections have been terminated, DB2 will then be able to eventually cancel or stop the dynamic location alias.
Temporary fix
Comments
APAR Information
APAR number
PI65090
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-29
Closed date
2016-08-03
Last modified date
2016-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI39885 UI39886
Modules/Macros
DSNLILNR
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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 September 2016