OpenLink ODBC Drivers running in debug mode ...

This posting is in response to the posting below, requesting information on how to enable Server side debugging of the OpenLink ODBC Drivers The OpenLink ODBC Scan utility can be used for tracing all ODBC calls being passed to the OpenLink or any other ODBC driver on the client machine, and is available from our WEB site (www.openlinksw.com) when you download our Windows ODBC client software. On the server the OpenLink Request Broker (oplrqb) can be started in debug mode to log all connections requests received from an OpenLink Client, and can be useful when debugging connection problems. Typically the Broker is started with the following options to provide the most debugging information: oplrqb +loglevel 7 +logfile <filename> Hope this helps. Regards, Hugh Williams OpenLink Software <Original message> >Paula Ramsay (pramsay@admin4.hsc.uth.tmc.edu) wrote: >: I'm looking for advice on the best ODBC drivers to use with my Informix >: data warehouse. Informix recommended Intersolv, but we've had some >: problems using it (duplicate data, etc...). Can anyone recommend some >: that we can demo? > >: Thanks, >: Paula Ramsay > > > Choosing an ODBC vendor/solution is a project in itself and > definitely there is no 'One size fits all': > > > We were using an HP product HP SOLID ODBC, exclusively, > but are now migrating our customers/developers to Openlink, with > both hp-ux odbc servers running simultaneously. > > We found some client issues with Intersolv(ease of setup, configuration,etc.), > that Openlink didn't have(at least in my case:-). > > And Openlink handles all new MS DSN file definitions with ease. > > Some of the my peeves about Openlink: > Server side logging is minimal; While it's not a life/death issue, I > really appreciate the details from our HP SOLID ODBC calls that are logged, > and that means Everything. > > Good luck! >-- >Ted Haasl-Martinez >CIM-Engineering >Hewlett Packard (VCD) >tedm@vcd.hp.com