×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Richard Schoen
Over QZDSAOINIT I would probably just stick to the
existing .Net/OLEDB or ODBC drivers.
Your logic sounds a bit circular in that ADO .Net, OLEDB, and ODBC drivers all interface with QZDASOINIT servers. I'm not aware of any other option, at any rate. Open socket, talk with QZDASOINIT server. So, if you're using the various interface options offered via IBM i Access, you're going "Over QZDASOINIT".
The same is true for PHP db2_ functions. They interface with QZDASOINIT jobs, using sockets.
That's why I was having a hard time following Brian's assertion about the "CGI interface" having more overhead than the "stored procedure interface". By "stored procedure interface", I gather that Brian meant the ODBC/QZDASOINIT interface provided by PHP's db2_ functions. In order to avoid confusion in the future, I'd suggest that we refer to the XMLSERVICE interface options as CGI, ODBC, and DRDA because all of them access XMLSERVICE through "stored procedures".
The real question is why would you use the ODBC/QZDASOINIT interface over the CGI interface?
Another question is, why might one use XMLSERVICE vs. ADO .Net, for example? I read an article by Erwin Earley that partially answered that. He shared an example of evoking the IBM i WRKSYSVAL, using XMLSERVICE, then displaying the list of system values in an HTML table.
I gather that there's some magic in XMLSERVICE that generates an XML response (i.e. a list of system values) from CL Commands like WRKSYSVAL. How would you do something like that with ADO .Net?
-Nathan.
midrange.com
