RE: Normalization was Left AS/400 and Returned

[Evan Harris <spanner@xxxxxxxxxx>]

Hi Joe

I understand that the SETOBJACC command allows a file to be "pinned" 
(cached might be a better term) in memory to avoid multiple disk accesses. 
Have you ever experimented with what performance benefits might be obtained 
using this method instead of the slightly less direct method of 
transforming the file into an array ?

Anyone else got any benchmarks or experiences ?

I'm just curious , not trying to prove a point or anything ;)

Regards
Evan Harris

> And I understand your preference.  Checking every date by doing a CHAIN
> or SETLL on a file is easy.  I think part of my bias is that I come from
> a scheduling background, which means I need information for periods,
> rather than single days.  I might have to schedule an operation to run
> over 10 days, and thus I'll have to know all the working days.  By
> reading a one-year array once, I'm covered and I can schedule all the
> work for that item.
>
> With a one-record per date approach, I'll be doing lots of I/O, over and
> over again (unless I read the data from the file into an array, at which
> point your argument about how hard it is becomes moot).
>
> I guess my point is that I think you need to look not only at the data
> but also at how it is used when determining the normalization of a
> database.
>
> Joe