Hit ODBC DB2 driver versus IBM ODBC driver for DB2 
Author Message
 Hit ODBC DB2 driver versus IBM ODBC driver for DB2

Hi, I have a rather peculiar little problem.

I installed IBM's own ODBC driver for DB2 (ver 7.1) on an NT 4.0 station and
connected the driver to a db2 base on MVS. After a couple of tries, it
finally connected. To test out the connection and doing some preliminary
test queries, I tried to link some tables in MS Access 97.

Problem #1:

In DB2 Connect, there is no way to filter out tables, or it does not work
properly. I wanted to show only tables with a prefix of
D100UOIP.<tablenames>. Anyone knows where to put in D100UOIP in the DB2
connect clientconfiguration. I have tried every thinkable parameter.

So I got every single table in the database (a lot of tables, I can tell
you) listed in the link table box in Access. I the marked out all those with
D100UOIP as prefix, and they all got linked in nicely. So far so good.

Problem #2:

When I tried to open a single table, some of the tables opened without any
problems (of course, the login box came first), and some table did not come
up so nicely. What happened here is kind of strange to me. When I clicked on
one of the "badly" behaved tables, the login box came up(even if it came up
once before), I logged in to MVS and pressed enter. Then, for each row in
the window, the login box multiplied automatically giving xx number of login
boxes. I could'nt possibly logon through every box, so I pressed cancel on
each box, and at the end, the table filled out all fields with #error or
#deleted or something. And then MS Access crashed.

Whatever I tried to do, it did not correct the problem. So I started looking
around for another ODBC driver, and found Hit ODBC driver from StarWare(?).
The had a 30 day license to try out the driver. I installed it, put D100UOIP
in the database owner field, and tried the same procedure in MS Acces as I
did for IBM's driver. And everything worked 100%. Only one login box came up
on the first table I tried to open, and it stayed open (MS Access did not
crash anymore)

I have another database tool I'm using for browsing through ODBC databases,
and that worked perfectly as well, listing only the tables with the prefix
D100UOIP.

Question: What it wrong here. How come IBM can't produce a stable and
working ODBC driver for their own DB2 running on their own machine?

Anyone had the same experience as I, and perhaps a solution. That would be
very much appreciated.

Thank you

Per Skjondal
Software Developer,
Bergen, Norway




Sun, 06 Jul 2003 02:48:08 GMT
 Hit ODBC DB2 driver versus IBM ODBC driver for DB2

Hi Per,

Regarding your Problem #2, I believe this will be fixed in FixPak 2 (coming
soon).  As a workaround, you can try setting the userid and password directly in
the db2cli.ini file for the data source you're connecting to.

Hope this helps.

Vivian

Quote:

> Problem #2:

> When I tried to open a single table, some of the tables opened without any
> problems (of course, the login box came first), and some table did not come
> up so nicely. What happened here is kind of strange to me. When I clicked on
> one of the "badly" behaved tables, the login box came up(even if it came up
> once before), I logged in to MVS and pressed enter. Then, for each row in
> the window, the login box multiplied automatically giving xx number of login
> boxes. I could'nt possibly logon through every box, so I pressed cancel on
> each box, and at the end, the table filled out all fields with #error or
> #deleted or something. And then MS Access crashed.



Sun, 06 Jul 2003 04:32:21 GMT
 Hit ODBC DB2 driver versus IBM ODBC driver for DB2
a number of these are problems with Access, not the IBM ODBC driver. I use
this all the time without problems. For looking at your tables etc you might
to look at the tool I use / wrote - Advanced Query Tool at
www.querytool.com.

Phil Castle.


Quote:
> Hi, I have a rather peculiar little problem.

> I installed IBM's own ODBC driver for DB2 (ver 7.1) on an NT 4.0 station
and
> connected the driver to a db2 base on MVS. After a couple of tries, it
> finally connected. To test out the connection and doing some preliminary
> test queries, I tried to link some tables in MS Access 97.

> Problem #1:

> In DB2 Connect, there is no way to filter out tables, or it does not work
> properly. I wanted to show only tables with a prefix of
> D100UOIP.<tablenames>. Anyone knows where to put in D100UOIP in the DB2
> connect clientconfiguration. I have tried every thinkable parameter.

> So I got every single table in the database (a lot of tables, I can tell
> you) listed in the link table box in Access. I the marked out all those
with
> D100UOIP as prefix, and they all got linked in nicely. So far so good.

> Problem #2:

> When I tried to open a single table, some of the tables opened without any
> problems (of course, the login box came first), and some table did not
come
> up so nicely. What happened here is kind of strange to me. When I clicked
on
> one of the "badly" behaved tables, the login box came up(even if it came
up
> once before), I logged in to MVS and pressed enter. Then, for each row in
> the window, the login box multiplied automatically giving xx number of
login
> boxes. I could'nt possibly logon through every box, so I pressed cancel on
> each box, and at the end, the table filled out all fields with #error or
> #deleted or something. And then MS Access crashed.

> Whatever I tried to do, it did not correct the problem. So I started
looking
> around for another ODBC driver, and found Hit ODBC driver from
StarWare(?).
> The had a 30 day license to try out the driver. I installed it, put
D100UOIP
> in the database owner field, and tried the same procedure in MS Acces as I
> did for IBM's driver. And everything worked 100%. Only one login box came
up
> on the first table I tried to open, and it stayed open (MS Access did not
> crash anymore)

> I have another database tool I'm using for browsing through ODBC
databases,
> and that worked perfectly as well, listing only the tables with the prefix
> D100UOIP.

> Question: What it wrong here. How come IBM can't produce a stable and
> working ODBC driver for their own DB2 running on their own machine?

> Anyone had the same experience as I, and perhaps a solution. That would be
> very much appreciated.

> Thank you

> Per Skjondal
> Software Developer,
> Bergen, Norway





Sun, 06 Jul 2003 07:04:49 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. IBM DB2 ODBC DRIVER : help !

2. Problems with IBM DB2 ODBC Driver

3. DTS & DB2 ODBC Driver Using DB2 Connect

4. IBM's DB2 JDBC driver and DB2/MVS

5. Developing IBMVA JDBC with NT DB2 driver to run on OS390 DB2 driver

6. Developing IBMVA JDBC with NT DB2 driver to run on OS390 DB2 driver

7. DB2 and the Hit Driver !

8. Replicating through DB2 ODBC driver

9. Microsoft ODBC driver for DB2 OS/390 and DTS

10. Where to find Microsoft odbc driver for DB2?

11. Security and ODBC driver to DB2

12. DB2 ODBC/OLEDB Driver


 
Powered by phpBB® Forum Software