OS/2, eCS & ArcaOS - Technical > Utilities


<< < (2/6) > >>

Sean Casey:

--- Quote from: Per E. Johannessen on April 18, 2023, 12:32:33 pm ---Do you know if the demo Intersolv SQL Server ODBC driver is available somewhere?

--- End quote ---

The Intersolv Microsoft SQL Server ODBC driver was not available in version 3.01, only in version 2.11.

Intersolv 2.11 SQL Server IVSS08.DLL  9/27/95
Intersolv 2.11 SQL Server IBSS08.DLL 7/15/96

The driver is included in both the DAX11.ZIP (IBSS08.DLL) and ODBCDEMO.ZIP (IVSS08.DLL) files on Hobbes.

I have been using the Sybase OS/2 Client SYBOS2.ZIP with SQL Server v.6.5 and v.4.2x

You can use the ODBC Installer ODBCINST3.ZIP to install the Intersolv driver.  This can also be found on Hobbes.  You must have ObjectRexx installed and enabled on your machine for the Installer to work.

Per E. Johannessen:
Found a link to ODBCINST3.ZIP at http://www.os2ezine.com/20010916/page_7.html but the link does not work anymore.
Not found at Hobbes either.

Martin Iturbide:

- ODBCDEMO.ZIP - Is now - DataDirectODBC_2-11.zip - INTERSOLV DataDirect ODBC Pack 2.11 Demo (1996-03-14)
- odbcinst2.zip - Is now - ODBC_1-03.zip

But I can not found any reference to a "ODBCINST3.ZIP" file that used to be in hobbes yet.

ODBC_1-03.zip Readme says:

--- Quote ---The ODBC Installer is an application for installing ODBC
Database Drivers, ODBC Administrator and ODBC Driver Manager.

To use the ODBC Installer unzip the file ODBCINST.ZIP into a directory.
That directory must be in your LIBPATH - OR - you LIBPATH must have the
path .; somewhere it it

example  LIPATH=.;C:\OS2;C:\OS2\DLL ......

The application was developed for a series of articles on ODBC
in OS2eZine - the OS/2 on line magazine  www.os2ezine.com
--- End quote ---

Sean Casey:
If you already have an ODBC manager and administrator installed, and have an ODBCINST.INI file, you can always use an INI editor to clone/edit any new entries.

I can't seem to find ODBCINST3.ZIP, but I have attached the ODBCINST2.ZIP file which automates the installation of the same demo ODBC drivers.

If someone has ODBCINST3.ZIP, it would be nice to have this uploaded to Hobbes.

Doug Clark:
The intersolv ODBC drivers were sold for OS/2, but I haven't been able to find retail versions for a couple of decades.  I also bought a set, probably from the same place Per E. Johannessen did, and they also were only windows.

As Sean Casey noted, you can use evaluation versions of Intersolv ODBC drivers with VIO/Command Line programs, such as Rexx/SQL ODBC.  This is because the evaluation versions put up a PM dialog box every 10 rows when fetching data to remind users to purchase the retail version.  If you aren't running in a PM session the dialog box never appears, although on older systems you might get a beep from the system speaker.  If you are running a PM program, such as StarOffice, with the Intersolv drivers you will get the reminder dialog box every ten rows.

As for other sources of ODBC drivers - commercial database vendors generally bundled ODBC drivers with their products.  These include Oracle, DB2, Watcom and SQLAnywhere.  In addition to those there are drivers that have been ported from the Linux world to OS/2, such as PostgreSQL, Sqlite, mySQL, etc.  Normally these are bundled with a ODBC Driver Manager/Administrator that have also been ported from Linux, such as from the UnixODBC or iODBC projects.  I have tested some drivers that were bundled with a Driver Manager from UnixODBC and what I found was the drivers work with either the Intersolv Driver Manager or the UnixODBC driver manager (as long as you respect version limitations), but the UnixODBC ODBC Administrator cannot administer Intersolv drivers - however the Intersolv Administrator can administer the UnixODBC version drivers.

ODBC version limitions
The ODBC API went through multiple versions - the major ones of concern to OS/2 are versions 2.x, 3.0, and 3.5.  The API specifies the functions that must be provided by a driver and how those functions operate.  Version 3 changed the names of many of the functions to align with standards, version 3.5 added functions for Unicode.

I should note that the version of the ODBC API that a driver, driver manager, and administrator is written to is not the same as the version number of the driver, driver manager or administrator.  For example the UnixODBC driver manager that is written to the API version 3.5 has many different release versions - as they discovered bugs or completed more of the driver manager they released new versions.

The ODBC API version restrictions are:  an application must connect to a driver written at its API version or higher.  A driver must connect using a driver manager at its API version or higher.  For example, an application written to the ODBC API version 2.x can connect to a driver written to ODBC API version 2.x or 3.0 or 3.5.  But an application written to ODBC API version 3 cannot connect with a driver written to ODBC API version 2.x


[0] Message Index

[#] Next page

[*] Previous page

Go to full version