How to get rid of SQLHost (DB2)

[Dave Rabelink]

We are using SqlHost for IBM's DB2 on mainframe for use with our CTD
applications.

Right now there are problems so we are curious if there is a simple way to
get rid of SQLHost to connect to the DB2 databases. I'm not a DBA expert and
know nothing about DB2 on mainframe but would like to ask this here if there
are others using this kind of setup without SqlHost.
What do we need to do on the Clients and on the DB2 side to get it working ?

Any help is appreciated !

[Martin Knopp]

 Posted by:  Martin Knopp 

I would suggest if its technically possible to use an OLEDB provider instead
of the ODBC driver - much better support in TD and much better core
technology.

[Dave Rabelink]

Yesterday i got the ODBC method working. It was easy, just add some info on
the server and in SQL.ini and our apps do connect and use the DB2 database
perfectly.

Only drawback is we have to install the DB2 client on the workstations and
configure the server.

Would OLEDB offer a better way then ?
Are there any settings to do on the DB2 server side ?
Do we need extra clients installed ?
Most importantly : do we need to change the SQL's then ?

Dave

[Lubos Vnuk]

 Posted by:  Lubos Vnuk 

Hi Dave,

I wrote an article about DB2 UDB ODBC connectivity which might be of some
help (no mainframe though):
http://sqlweb.vnuk.org/gup/articles/db2cnt.html

Lately I have found an ODBC connection string that might do without DSN
creation but I haven't tried it:
"driver={IBM DB2 ODBC
DRIVER};Database=myDbName;hostname=myServerName;port=myPortNum;protocol=TCPI
P; uid=myUserName; pwd=myPwd"
Please let me know if you get any success with this one.

Regards,
Lubos.