×
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 would imagine though, IF all you cared about was the existence check,
then SETLL would still be the winner since it only involves a trip to the
index, while chain requires a trip to the index, the table-space and a load
of the data. Make sense?
It might make sense - but some tests I ran about 12 months ago indicated
that CHAIN was actually faster than SETLL.
In my tests "misses" outnumbered hits 9 to 1. This was done with 100,000
records in the file - key length of 7 digits generated randomly in the range
1 - 1,000,000. Program then ran 1,000,000 randomly generated keys against
the DB. Ran test multiple times - if I recall correctly CHAIN outperformed
SETLL by 5 - 10% in this scenario. This on a V5R3 system.
Jon Paris
Partner400
www.Partner400.com
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
