|
>Of course, OPNQRYF itself uses the same >underlying SQL support, so I wouldn't have included it in the same family as >the native opcodes. John Taylor This is the point of my post. OPNQRYF has UP TO now used the same engine underneath for the optimizer. BUT in the not to distant future(V5R1 ? even?) The enhancements to the optimizer will mostly affect SQL. OPNQRYF and SETLL, READE, etc will (I believe from my sources) remain "as is" in methodology and speed. Joe, your post in speed neglected the fact that both OPNQRYF and SQL take advantage of Indexes (whether created via the CRTLF or CREATE INDEX ) John Carr
As an Amazon Associate we earn from qualifying purchases.
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.