From: Tim H. <th...@op...> - 2005-12-09 18:43:39
|
On 9 Dec 2005, at 02:31, Yumiko Izumi wrote: > It is a question about the procedure which accesses DB2 UDB via iODBC. > It is that the following accesses are realized by ODBC on us now. > It thinks. "iODBC" is used for the ODBC driver manager. > 1) Unix DB2 UDB (local) > 2) Unix DB2 UDB(client) => Windows DB2 UDB > Although it is going to realize each in the procedure investigated > by WEB etc. > It is in the state where became errors, such as IM003 and IM008, > and it has failed. > Then, we want to check a procedure etc. again and it contributes. > Wanting to know is [ following ] a point. > - Setup required for the DB2 UDB side > - The ODBC driver and setup of DB2 UDB > libdb2.a suited the machine. > - Setup by the side of iODBC > Description of odbcinst.ini and odbc.ini > - Others > Thanks in advance. Hi, The general comments concerning ODBC component architecture and odbc.ini in my response to your other mail also apply here. In this case, you need an ODBC driver for DB/2, and you need to set the environment variables DB2DIR and DB2INSTANCE. If you're using the OpenLink driver, http://docs.openlinksw.com/st/unixliteconf.html#unixlitedb2 should help. Can you tell us what OS you're on (looks like AIX?) and supply the full error messages and odbc.ini from your failed connections please? HTH, ~Tim -- Tim Haynes Product Development Consultant OpenLink Software <http://www.openlinksw.com/> |