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 IC63990 Status: Closed

IMPORT & EXPORT FROM DB2 LUW CLIENT TO DB2 Z/OS SERVER OR OTHER HOST
SERVERS RETURNS SQL2019N BECAUSE PACKAGE NOT BOUND

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If you attempt to use the Import or Export utilities from a 
DB2 LUW 9.5 client to a DB2 on z/OS, DB2 on VSE, DB2 on VM, or 
DB2 on iSeries server you may encounter a SQL2019N. 
 
Prior to v95, binding the list file ddcsmvs.lst, ddcsvse.lst, 
ddcsvm.lst or ddcs400.lst  was sufficient 
to use these utilities from a DB2 LUW client to a DB2 on z/OS, 
DB2 on VSE, DB2 on VM or DB2 on iSeries server respectively. 
 
However in V95 a new package named db2uiDescribe.bnd 
was introduced in Import & Export. This package was correctly 
added to db2ubind.lst (for DB2 LUW servers), but not to 
ddcsmvs.lst (for DB2 on z/OS servers), or to ddcsvse.lst (for 
DB2 on VSE servers), or to ddcsvm.lst (for DB2 on VM servers), 
or to ddcs400.lst (for DB2 on iSeries servers). 
 
The APAR fix involves adding db2uiDescribe.bnd to the 
ddcsmvs.lst, ddcsvse.lst, ddcsvm.lst, and ddcs400.lst list 
files.
Problem Summary:
IMPORT & EXPORT FROM DB2 LUW CLIENT TO DB2 Z/OS SERVER OR OTHER 
HOST SERVERS RETURNS SQL2019N BECAUSE PACKAGE NOT BOUND
Local Fix:
You can manually bind db2uiDescribe.bnd.
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.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 6 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
First Fixed in DB2 Version 9.7 Fix Pack 1
Workaround
The workaround is to manually bind the db2uiDescribe.bnd file to 
the database. 
 
Example: 
This example illustrates how to bind the db2uiDescribe.bnd file 
contained in the db2inst1 instance to the sample database when 
logged in as the instance owner. 
 
cd \db2inst1\sqllib\bnd 
db2 terminate 
db2 CONNECT TO sample 
db2 bind db2uiDescribe.bnd BLOCKING ALL GRANT PUBLIC ACTION ADD 
db2 terminate
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
15.12.2009
08.10.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList