Openlink and IDS 7.3 and esql
Posted in 2000
Topics: Installation, Setup & Upgrades, Connectivity: ODBC / JDBC / .NET, Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues, Versions, Editions & End-of-Life
I'm having an enormously frustrating time trying to get Openlink (3.2 Win95 and Linux clients) to talk to Informix 7.3 on SCO 5.0.5a. The Openlink broker comes up OK and in debug mode reports a successful connection when a client logs in. Even the client 'test' utility reports 'Success!' when run. After that, however, any sql or in fact any rubbish at all gives me S1000 ODBC Driver General error. This occurs on all clients of both types of OS. The thing is that the server portion of Openlink (still running in debug mode) appears to not even see the SQL request and no additional lines are added to the debug log. After relinking the Openlink agent, quadruple checking my environment, running it as root and informix, reinstalling several times on several machines, and talking/posting to Openlink staff, I have been told that one of the things to try is to relink the agent against ESQL 7.2 libraries. I have ESQL 9.1 in my IDS 7.3 distribution. After speaking to Informix Australia, I am told that these 'old' libraries are no longer available as a general rule, and that I would have to purchase them in any case, something I am reticient to do considering that Openlink is listed as being Informix 7.3 capable. My question is; has anyone been successful in marrying Openlink 3.2 to Informix 7.3 (especially on SCO 5.0.5)? If so, is there another workaround besides hunting down and paying for old libraries that will likely not be required at the next release of Openlink? There's not even any guarantee that these older libraries are the answer, which makes me even more unlikely to fork out cash for them. Failing that, has anyone a recommendation for middleware in my environment. I am trying to get a PHP app up (Linux/PHP 3.0.14) using ODBC to talk to the database (IDS 7.3, SCO OS 5.0.5). The Win95 clients are more of a bonus than a necessitity. I know I can rewrite the PHP calls using Informix SDK and native functions (which incidentally works fine, thereby at least verifying my network setup), but that would be a large job if Openlink or other ODBC drivers can be used for my purposes. Many TIA Bryan Tonnet
In article <38ED3604.76A57366@phase4.com.au>, batonnet@phase4.com.au says... > My question is; has anyone been successful in marrying Openlink 3.2 to > Informix 7.3 (especially on SCO 5.0.5)? If so, is there another Yes, but on Linux. It may or may not mean anything, but in my experience 40% of all Informix related bugs/problems are on SCO. > Failing that, has anyone a recommendation for middleware in my > environment. I am trying to get a PHP app up (Linux/PHP 3.0.14) using > ODBC to talk to the database (IDS 7.3, SCO OS 5.0.5). Why are you using ODBC for that at all? PHP have very solid native Informix connectivity? > The Win95 clients > are more of a bonus than a necessitity. If you don't plan to do "wired" stuff and have hundreds of ODBC clients, Informix ODBC driver will do just fine. It uses I-net connection, so it does not need anything additional on the server. > I know I can rewrite the PHP > calls using Informix SDK and native functions (which incidentally works > fine, thereby at least verifying my network setup), but that would be a > large job Large job? > if Openlink or other ODBC drivers can be used for my purposes. Why on earth? Compatibility with other ODBC databases? Dream on... If you really need that, it is better to take a look at database abstract layers for PHP (there are several, and most will do a good job of preserving database abstraction while maintaining performance gains of native connectivity.). Other then that, I would recommend that you talk with OpenLink support people one more time. Escalate. This guys have one of best support people in the industry, talk to them. -- Yours, Andrej Falout, http://www.falout.com ICQ 7628616 ++64.21.607517 #----------------------------------------------------------------- globals "std_disclaimer.4gl" Ask yourself just one question: ' Qu' m's se puede hacer y aprender ? - Propellerhead ReBirth RB-338 manual
Andrej Falout wrote: > Why are you using ODBC for that at all? PHP have very solid native > Informix connectivity? I'm sure you're right, but the application is written with ODBC calls, and if I can get away with not changing it, and the problems of then being unsupported by the software house, then so much the better. If I have to, I'll go down this path. > > I know I can rewrite the PHP > > calls using Informix SDK and native functions (which incidentally works > > fine, thereby at least verifying my network setup), but that would be a > > large job > > Large job? Relatively. If I can get Openlink to work, then I need not change anything. > Why on earth? Compatibility with other ODBC databases? Dream on... That was something I had thought possible.... > Other then that, I would recommend that you talk with OpenLink support > people one more time. Escalate. This guys have one of best support > people in the industry, talk to them. OK, I'll do that. So far I have not been swamped with support from them, but they've not been unresponsive either. Thanks Bryan Tonnet