DB2 - Problembeschreibung
Problem IC88341 | Status: Geschlossen |
CALLING STORED PROCEDURE ON NON-LUW DATABASES FAILS TO RETURN THE RETURN CODE WRITTEN IN THE STORED PROC | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
When calling a stored procedure located on a non Linux/Unix/Windows database server such as z/OS and i-Series the return code inside the stored procedure is not returned. The output below should return "RETURN STATUS: 1000" since this was coded in the stored procedure. Instead the incorrect output "RETURN STATUS: 0" is returned. connect to sample user db2inst1 using Database Connection Information Database server = DB2 z/OS 9.1.5 SQL authorization ID = DB2INST1 Local database alias = SAMPLE CREATE PROCEDURE TEST (OUT ID INTEGER) RESULT SETS 1 LANGUAGE SQL DISABLE DEBUG MODE P1: BEGIN DECLARE cursor1 CURSOR WITH RETURN FOR SELECT c1 from t1; -- If OPEN cursor1 is commented out the expected rc=1000 is returned OPEN cursor1; RETURN 1000; END P1 DB20000I The SQL command completed successfully. call test(?) ID: NULL C1 "TEST" RETURN_STATUS: 0 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 Fix Pack 2 or higher. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 V10.1 Fix Pack 2. This should be applied to the DB2 Connect system used to establish connectivity to non Linux/Unix/Windows database servers such as z-Series and i-Series. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.11.2012 19.04.2013 19.04.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.2 | |
10.5.0.2 |