At 11:39 PM 12/5/97 EST, you wrote:

>No, your records will not necessarily be returned based upon the S/O
>SQL evaluates the n (used to be five, may now be ten or more) oldest logical
>files by creation date based upon the ORDER BY and WHERE clauses to decide
>whether or not it needs to build an access path.  If you have an ORDER BY
>statement that doesn't match the WHERE (select/omit) and key of those older
>logicals, you may not get the logical specified in your SELECT statement.
>Again, issue STRDBG during testing prior to invoking your imbedded SQL
>and display the job log after invocation -- this will show you whether an
>access path was selected or built...

Do you have an example where you got MORE records than the S/O criteria
allowed, even when you named the S/O logical in the SELECT statement? and
even when the access path chosen was different from that of the S/O logical?


Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "".
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].