×
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.
I won't say it! ;-)
If you go deep enough, everything uses storage management tasks in SLIC.
But we don't get to see most of that. The thing to look at is the call
stack while using native IO and again while running SQL. And when you get
to V5R2 and up, you need to check whether you end up going through the
classic query engine (CQE) or the new one (SQE). You will see completely
different code paths. Yes, records are mostly read with QDBGETM, etc., but
there's a lot above that in the call stack that will differ between native
and SQL. Getting there is half the fun!
Vern
At 11:19 AM 7/23/2004, you wrote:
Who doesn't say that traditional I/O and SQL aren't the same under the
covers? Maybe they are. After all, sooner or later it boils down to
accessing the IOP. It's just what wrappers are used, eh?
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
