ODBC connects to the local SQL implementation, for z/OS there is only Db2 for z/OS. In theory the C/C++ application program with ODBC calls coded could run unmodified on Linux or Windows with the same ODBC calls, after recompilation (of course this kind of platform independence is very hard to achieve). The ODBC goes to the local SQL implementation, such as SQL Server. The communication layer for Db2 on z/OS is DDF or DRDA and this is unrelated to ODBC but the ODBC requests can flow on it (just like they flow on TCP/IP). This is standard part of Db2 so nothing more to install, however there are add-on products to enrich the solution. The Linux/Windows end typically has both DDF and DRDA software already installed but Microsoft sells HIS (host integration server). From an application standpoint, there are superior solutions to using ODBC, which is now a very old, legacy and almost obsolete solution. For db2 remote data, using 3 part database name is what applications generally use, for example.
On Sun, Aug 25, 2024 at 7:00 PM Binyamin Dissen < 00000662573e2c3a-dmarc-requ...@listserv.ua.edu> wrote: > ODBC is only good for connecting to DB2? > > Lets say that I want to connect to an arbitrary RDMS on an arbitrary > platform, > such as MYSQL or M%crosoft database on Windows from MVS. > > Does JDBC work out of the box? Is software required on MVS or Windows to > allow the connection? > > > > On Fri, 23 Aug 2024 00:45:06 +1000 Attila Fogarasi > <000005b6fee9abb7-dmarc-requ...@listserv.ua.edu> wrote: > > :>ODBC is a programming API for application programs written in C/C++ to > use > :>as an alternative to SQL. It isn't a connection protocol to a remote > :>database server. That connection can be a variety of ways, such as DRDA > or > :>Db2 Connect (that is a gateway) ... it all depends upon the specific > remote > :>system you want to use. JDBC is often more convenient as it is a > :>newer/more powerful protocol than ODBC (ODBC is over 30 years old now). > :>It's a bit unusual to run C/C++ application in z/OS to access non-z/OS > SQL > :>databases using ODBC, depending upon UOW and 2 phase commit requirements > :>there can be better solutions than ODBC. Db2 z/OS does have some special > :>connectivity to remote Db2 systems including LUW with/without ODBC, a bit > :>easier than to non-Db2 Unix or WIndows systems. > :> > :>On Wed, Aug 21, 2024 at 1:12?AM Binyamin Dissen < > :>00000662573e2c3a-dmarc-requ...@listserv.ua.edu> wrote: > :> > :>> It would seem that this would be controlled by the DSNAOINI (based on > the > :>> DSN8OIVP). > :>> > :>> It is not clear to me if (1) how to specify the remote non-DB2 > connection > :>> and > :>> (2) if special software is required. For example, while I can find > MYSQL > :>> ODBC > :>> for various platforms, I do not see a ZOS version. Are MVS drivers > :>> required to > :>> be installed for each database type? > :>> > :>> -- > :>> Binyamin Dissen <bdis...@dissensoftware.com> > :>> http://www.dissensoftware.com > :>> > :>> Director, Dissen Software, Bar & Grill - Israel > :>> > :>> ---------------------------------------------------------------------- > :>> For IBM-MAIN subscribe / signoff / archive access instructions, > :>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > :>> > :> > :>---------------------------------------------------------------------- > :>For IBM-MAIN subscribe / signoff / archive access instructions, > :>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > Binyamin Dissen <bdis...@dissensoftware.com> > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
