DB2 FOR LUW / DB2FORLUW / A10 - DB2

When LIKE clause is used in a SELECT statement, and the value 
specified for the LIKE clause appears in the statement again, 
then CLPPlus is wrongly replacing this value with the dummy 
string, and hence the SQL fails. 
 
Example: 
 
SELECT * 
FROM   tab01 
WHERE  val1 LIKE 'AAA' AND 
       val2 = 'AAA' 
 
It will cause SQL0206N like this. 
SQL0206N  "CLPPLUS976LIKEHNDLMCN0070" is not valid in the 
context where it is used. 
 
Using V10.1 FP3 or earlier Fix Packs, we will not get SQL0206N, 
but the query sent to the server might be invalid.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using CLPPlus                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Customer facing this issue should upgrade to DB2 10.1 FP5    * 
****************************************************************

Set the "environment variable substitution" off by: 
 
set envvarsubst off;

This problem has been fixed in DB2 10.1 FP5

not known / see Local fix

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

25.08.2014
17.07.2015
17.07.2015