Sean and I have been conversing through messenging on the site about DB2/2 and WinOS2 and IBM's WinOS2 CAE.
I wrote an article a number of years ago about databases and ODBC. In that article I said that the DB2 version 5 CAE for WinOS2 did not work very well, and that IBM had instituted a "2 versions back, 1 version forward" policy on CAEs and server versions. This meant that the DB2 version 2 WinOS2 CAE and ODBC driver, which works well in WinOS2, would not work connect with DB2 version 7. All of that, to the best of my knowledge, is still true.
I have discovered since then however what appears to be a work around for getting the version 5 DB2 CAE and ODBC driver for WinOS2 to work - which means you can connect from WinOS2 to DB2 version 7 - which is the last version of server released for OS/2.
The work around that appears to work is to install the DB2 version 5 CAE for Windows 3.1, connect to your database using the IBM WinOS2 Command Line Processor in a WinOS2 session, and leave the command line processor running and connected, before attempting to connection with any other application.
(This is an obvious issue when attempting to connect Windows 3.1 applications to DB2 in a seamless session. I think I have a work around for that also but it is not ready yet.)
The second issue Sean had was running ReportSmith in WinOS2 and connecting to DB2. ReportSmith is, in my opinion, and excellent report writer, very cheap and readily available. It is bundled with Delphi versions 1 and 2 which you can pick up on ebay for $5 - $15. The trick in getting ReportSmith to connect to DB2 is to remove the word DB2 from the description of the driver in ODBC.INI and ODBCINST.INI located in C:\OS2\MDOS\WINOS2. I have attached my ODBC.INI and ODBCINST.INI to show how it is done. The thing to remember however is the IBM DB2 Client Setup won't work unless the DB2 is in the description. So get the client setup, THEN alter ODBC.INI and ODBCINST.INI.
Hope this helps Sean