From: <Jim.Nelson@RCIS-NET.COM> > there is a performance monitoring tool that logs, in great detail, > the QZDASOINIT jobs. This showed each statement, and how > long it took to complete it. On the client side, you can use the ODBC data source configuration tool, in the control panel, to turn trace on. The resulting log file often provides an indication of poorly structured SQL calls. It's possible that the Client Access ODBC driver isn't handling poorly structured calls as well as the SQL Server driver. Remember, the trick with ODBC is to reduce the number of interactions with the server by means of optimized calls. Often the server performs well, but is doing a lot of unnecessary work. The Client Access Express for Windows ODBC User's Guide offers a number of performance tips. On the other hand, if you'd be interested in effective tools for deploying high-performance, interactive Web applications on your AS/400, I'd encourage you to contact me privately. Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.