DB2 FOR LUW / DB2FORLUW / 970 - DB2

A DB2 client application may abend with the following call stack 
: 
 
  sqleuBindParametersForServerActivation 
 
  sqleuInvokeActivationRoutine 
  sqleuPerformServerActivationCheck 
  sqleUCappConnect 
  CLI_sqlConnect 
  SQLConnect2 
 
The top function may not show on the stack as it depends on the 
operating system. 
Some platforms may fail with a SIGILL ( illegal instruction ) 
instead of an expected SIGSEGV - segmentation violation. 
 
This problem occurs when the client code connects directly to 
the DB2 z/OS server and does not use a DB2 Connect Gateway. 
This problem was introduced since DB2 V9.7 Fix Pack 3a via the 
feature described here : 
 
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.i 
bm.db2.luw.licensing.doc/doc/t0057375.html 
 
However regardless of whether the license is activated on the 
server side, the problem can occur.

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 connect server to v9.7 Fix Pack 10 or        * 
* higher.                                                      * 
****************************************************************

Connect via a DB2 Connect Gateway

This problem was first fixed in V9.7 Fix Pack 10

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

29.01.2014
08.12.2014
08.12.2014

9.7.FP10