RE: Database Access Path Question

["David Dunfield" <ddunfie@xxxxxxxxxxxx>]

DYNSLT may be an option, but we have experienced less than great 
results using dynslt in reading records. It does work, but it still 
reads all records in access path to select only those DYNSLT.

> Hi Nelson,
> 
> Use "dynslt".  that tells the system to build the complete access 
path ( all
> records ) and then dynamically select records at i/o time.
> 
> Steve
> 
> -----Original Message-----
> From: midrange-l-bounces@midrange.com
> [mailto:midrange-l-bounces@midrange.com]On Behalf Of Smith, Nelson
> Sent: Thursday, February 06, 2003 9:39 AM
> To: midrange-l@midrange.com
> Subject: Database Access Path Question
> 
> 
> Check my thinking on this.....
> 
> If I have a logical with 7 key fields and a select/omit field 
selecting a
> particular code, and I create a new logical with the same key fields 
and
> select/omit field but selecting out a different code, will the new 
logical
> share the seven-key-fields part of the access path with the first 
logical?
> 
> It would seem NOT to me, since the select/omit field is in reality 
just an
> initial key.  In fact, if it were listed first in an eight-field key 
list, I
> would have been able to SETLL and READE on either code and then the 
rest of
> the 7 keys. Doesn't this mean that the two logicals would never share 
an
> access path even though they use the same seven keys?  Or, is the 
database
> smarter than that?
> 
> Nelson Smith
> nsmith@lincare.com
> ncsmith@tampabay.rr.com
> 
> 
> 
> 
************************************************************************
****
> 
************************************************************************
****
> ****************************************************
> This message originates from Lincare Holdings Inc. It contains 
information
> which may be confidential or privileged and is intended only for the
> individual or entity named above.
> It is prohibited for anyone else to disclose, copy, distribute or use 
the
> contents of this message.
> All personal messages express views solely of the sender, which are 
not to
> be attributed to Lincare Holdings Inc., and may not be copied or 
distributed
> without this disclaimer.
> If you received this message in error, please notify us immediately at
> MailAdmin@lincare.com or (800) 284-2006.
> 
************************************************************************
****
> 
************************************************************************
****
> ****************************************************
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 

Dave Dunfield
Midwest Integrated Systems Resources
AS/400  and LANSA Expert
PO Box 1481
Portage, MI 49081
 
Phone-269-373-3049 Cell 269-501-5685