home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC96705 Status: Closed

IMPLEMENTATION FIELD IN SYSCAT.ROUTINES FOR A SOURCED FUNCTION MISSING
MODULE NAME

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The following examples display the behavior.   Please note that 
this APAR was incorrectly raised and included in DB2 10.1 
Fixpack 4 and is being cancelled through IT03012 
 
CREATE OR REPLACE FUNCTION R1.F1() 
SPECIFIC F1 
RETURNS INT 
RETURN 1 
DB20000I  The SQL command completed successfully. 
 
CREATE OR REPLACE FUNCTION R1.F2 ( ) 
RETURNS INTEGER 
SOURCE R1.F1() 
DB20000I  The SQL command completed successfully. 
 
CREATE OR REPLACE MODULE R1.M1 
DB20000I  The SQL command completed successfully. 
 
ALTER MODULE R1.M1 
PUBLISH FUNCTION F1() 
SPECIFIC F1 
RETURNS INT 
RETURN 1 
DB20000I  The SQL command completed successfully. 
 
CREATE OR REPLACE FUNCTION R1.F2M ( ) 
RETURNS INTEGER 
SOURCE R1.M1.F1() 
DB20000I  The SQL command completed successfully. 
 
SELECT SUBSTR(ROUTINESCHEMA,1,5), SUBSTR(ROUTINENAME,1,5), 
SUBSTR(IMPLEMENTATION,1,10) FROM SYSCAT.ROUTINES WHERE 
ROUTINESCHEMA = 'R1' AND ROUTINENAME IN ('F2', 'F2M') 
 
1     2     3 
----- ----- ---------- 
R1    F2    R1.F1 () 
R1    F2M   R1.F1 () 
 
  2 record(s) selected. 
 
The second row should read R1.M1.F1() for the IMPLEMENTATION.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First changed in DB2 10.1 Fixpack 4 but this change is being * 
* rolled back to previous behavior via APAR IT03012            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First changed in DB2 10.1 Fixpack 4 but this change is being 
rolled back to previous behavior via APAR IT03012
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.10.2013
08.07.2014
09.07.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList