DB2 FOR LUW / DB2FORLUW / 970 - DB2

Another symptom is that users executing ALTER PROCEDURE will 
have the Line Feed (0xA) character removed before the DDL is 
sent to the server.  Thus when the DDL is retrieved the entire 
CREATE PROCEDURE statement will be one long line with no new 
line or carriage returns. 
 
Example: 
alter procedure db2inst1.sp1 replace version v1 () 
    DISABLE DEBUG MODE 
    ISOLATION LEVEL CS  /* if there is a ' or " in this comment 
no LF is sent*/ 
    LANGUAGE SQL 
    P1: BEGIN 
    -- Test Insert 
    INSERT INTO T1 VALUES( 
            11, -- here ' or " has no problem. 
            55) --Parm2 
    ; 
    -- end of procedure 
END P1@ 
 
select * from /* it is new 'style comment */ 
 -- normal comment 
 T1@ 
 
The problem is with /* ... */ style of comment only.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See ERROR DESCRIPTION.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 Fixpack 5.                                   * 
****************************************************************

Do not use single quotes (') or double quotes (") inside a new 
style comment.  Another alternative is to use the old style 
comments instead (e.g. -- Line 1)

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 v9.7 Fixpack 5.  At minimum the 
fix should be applied to where the SQL statements are executed. 
This may be a remote client or the local DB2 server.

SEE LOCAL FIX.

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

09.05.2011
19.01.2012
19.01.2012

9.7.FP5