|
Problem IC63367
|
Status: Closed |
CALLING A Z/OS STORED PROCEDURE WITH NULL INPUT PARMS FROM A JAVA PROGRAM, JCC T2 OR T4, RESULTS IN ERRORCODE=-4463 |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
Customer using JDBC JCC T2/T4 to call a z/OS DB2 Stored
Procedure. They are using a NULL input parameter which results
in a -4463 error code returned.
To recreate the error use the SP below being called is a single
line test SP.
CREATE TABLE TEST (ID CHAR(20))!
CREATE PROCEDURE TEST.SP_TEST
(IN id CHAR(20))
LANGUAGE SQL
BEGIN
INSERT INTO TEST VALUES ('SP_TEST called');
END!
The CALL statement is coded as:
CALL SP_TEST(NULL).
The result is:
Error parsing literal value starting at index 21. Error
Detail:
Invalid character 'N' found in literal. Full SQL
statement
text=CALL SP_TEST(NULL) ERRORCODE=-4463, SQLSTATE=42601. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users connecting to z/OS DB2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* When using Universal JDBC driver, JCC T2/T4, to call a *
* z/OSDB2 Stored Procedure, if the input parameter has 'NULL' *
* asits value the result will be a -4463 error code *
* beingreturned.To recreate the error use the SP below being *
* called is asingle line test SP.CREATE TABLE TEST (ID *
* CHAR(20))!CREATE PROCEDURE TEST.SP_TEST(IN id *
* CHAR(20))LANGUAGE SQLBEGININSERT INTO TEST VALUES ('SP_TEST *
* called');END!The CALL statement is coded as:CALL *
* SP_TEST(NULL).The result is:Error parsing literal value *
* starting at index 21. ErrorDetail: Invalid character 'N' *
* found in literal.Full SQL statement text=CALL SP_TEST(NULL) *
* ERRORCODE=-4463,SQLSTATE=42601. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 Fixpack 2. *
**************************************************************** |
| Local Fix: |
Use the Legacy Type 2 JDBC driver using db2java.zip. |
| available fix packs: |
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.7 Fix Pack 1 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.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 6 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 was first fixed in Version 9.7 Fixpack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.09.2009
30.06.2010
30.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
