|
Reading through all records with optimized blocking would probably perform better than Setll, Read, etc. If you declare the file with Block(*Yes), and override the block size, you should do better performance-wise than doing lookups/cursor positioning using SetLL. Basically, using the record length, figure out how many records will fit in 128k, and override the file before opening (OVRDBF SEQONLY(*YES ####) ). Perform only READs against this file, and it should go pretty fast. Otherwise, you might build a clever SQL statement, with well-thought-out indexing, and do a little better. On 8/18/05, Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote: > > Can below be done without having to read thru each record in detail > file(Telephone Master)? > > I need to summarize a big telephone master file (22M+) into ranges. I'm > attempting to use read, reap, setll to avoid the need to read each phone > number record to create this summary file. However, no luck so far. > > The detail file looks like below: > AreaCode Prefix Suffix Terminal > 601 123 0001 JSN > 601 123 0002 JSN > 601 123 0003 JSN > 601 123 0004 JSN > 601 123 0009 BTD > 601 123 0010 BTD > 601 123 0044 BTD > 601 123 0091 JSN > 601 123 0092 JSN > . > . > . > > > The summary file is by AreaCode, Prefix, Terminal, From Suffix, to Suffix. > Using above data, the result should be as follow: > AreaCode Prefix Terminal From Suffix to Suffix > 601 123 JSN 0001 0004 > 601 123 BTD 0009 0044 > 601 123 JSN 0091 0092 > > > -- > 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. > >
As an Amazon Associate we earn from qualifying purchases.
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.