DB2 FOR LUW / DB2FORLUW / 970 - DB2

This is not a regression.  This defect is simply used to keep 
track of minor problem that PSM/Unified Debugger needs to solve 
in the future release. 
 
When you debug the below function, the debugger does stop at 
"RETURN v1;" or the first line "CREATE FUNCTION..." statement to 
let the user viewing v1's value before existing debug. 
 
CREATE FUNCTION FOO(IN pin INTEGER) 
RETURNS INTEGER 
BEGIN 
    DECLARE v1 INTEGER; 
    DECLARE v2 INTEGER DEFAULT 100; 
 
    SET v1 = pin * pin; 
    RETURN v1; 
END 
 
There is a similar problem in debugging procedure below.  The 
user can't view v1's value before existing debug session. 
 
CREATE PROCEDURE FOO(IN pin INTEGER) 
 
BEGIN 
    DECLARE v1 INTEGER; 
    DECLARE v2 INTEGER DEFAULT 100; 
 
    SET v1 = pin * pin; 
END 
 
To solve this problem, all DB2z, iSeries, and IDS debugger stop 
at the first line CREATE PROCEDURE or CREATE FUNCTION

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
 

not known / see Local fix

This is an extremely minor issue that has been rectified.

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

07.09.2011
20.09.2011
20.09.2011