Re: Memory Allocation Question

This might be an instance where SQL may be one of your better options.
Especially if you were to create an Encoded Vector Index over each of
your three fields. I couldn't tell you off hand how to code your SQL
statements to accomplish your task, but you should probably take a look
at it as an option.

Joe Lee

>>> rduz-midrange@xxxxxxxxxxxxxxxxxxx 11/09/2004 13:40:24 >>>
On Tue, 2004-11-09 at 15:28, Tony Carolla wrote:
> Thanks Rich.  
> 
> My second attempt (which I didn't tell about -- I was trying to
avoid
> a novel ;) did just that.  I made a discovery though, that over 50%
of
> people have the same ss# -- Zero.   
Right, the SS index should not include records where the SS is 0, 0
means not given.  Course on the systems I work on, the SS is required,
so the bogus records have a SS# = 1.  Anyway, simply create the SS
logical with a select/omit criteria, and only select those records
that
have an SS.  Same for birthdate, btw.

I think you will be able to save *many* I/O's and much processing time
by using the three indexes idea.


--
Regards,
Rich

Current Conditions in Des Moines, IA
Broken Clouds
Temp 62.6F
Winds out of the Southwest at 16mph

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l 
or email: RPG400-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.