KevinHarrison 1000005N52 Visits (4313)
Overview:PM54383 solves this condition, in V9 and higher, but only targets the condition WRT TCP/IP related connections.
If an application executes SQL that refers to a remote site but, for what ever reason, the operator/user wants to cancel the associated DB2 thread or application, the cancel of the DB2 thread will not be fully effective until the remote system actually replies with its SQL answer (and depending on the SQL, that could be a long time). This is a historical deficiency with DB2 cancel processing, and is documented in the CANCEL THREAD Usage Notes in the DB2 Command Reference manual and a procedure was provided on how to use network stack (VTAM or TCP/IP) commands to kill the connection with the remote site. This procedure works but could be cumbersome.