|
Problem IC63611
|
Status: Closed |
EXECUTION OF STORED PROCEDURE ON Z/OS WITH NULL INPUT PARAMETER INSERTS STRING "NULL" INSTEAD OF NULL VALUE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When executing a Stored Procedure on z/OS DB2 when input
parameter is null, this will result with string NULL inserted as
opposed to a null character.
For example.
db2 => create procedure sptest2(IN id char(20)) language sql
begin insert into test values (id, 10); end
db2 call sptest2(null)
db2 select * from test
A B
-------- -----------
null 10 ===> A string
"null" value is inserted
If you instead insert into the table
insert into test values (null, 8) ===> this actually inserts a
SQL null value in the table
db2 select * from test
A B
-------- -----------
- 8 ==> The "-" is showing
as null under column "A"
So the null character is shown and not the string null. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 Connect to z/OS DB2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* When executing a Stored Procedure on z/OS DB2 when input *
* *
* parameter is null, this will result with string NULL *
* inserted as *
* opposed to a null character. *
* *
* *
* *
* For example. *
* *
* db2 => create procedure sptest2(IN id char(20)) language sql *
* *
* begin insert into test values (id, 10); end *
* *
* *
* *
* db2 call sptest2(null) *
* *
* *
* *
* db2 select * from test *
* *
* *
* *
* A B *
* *
* -------- ----------- *
* *
* null 10 ===> A string *
* *
* "null" value is inserted *
* *
* *
* *
* If you instead insert into the table *
* *
* *
* *
* insert into test values (null, 8) ===> this actually *
* inserts a *
* SQL null value in the table *
* *
* *
* *
* db2 select * from test *
* *
* *
* *
* A B *
* *
* -------- ----------- *
* *
* - 8 ==> The "-" is *
* showing *
* as null under column "A" *
* *
* *
* *
* So the null character is shown and not the string null. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 fixpak 1. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 9.7 Fixpak 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.10.2009
19.01.2010
19.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.,
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
| 9.7.0.1
|
|
