RE: Chaining with a very large file

Douglas,

As long as you don't do things that try to build access paths dynamically
(such as SQL or OPNQRYF) and you stick to keyed access in RPG, you should be
fine.  I would think that breaking this down into smaller units would only
increase the hassles of managing these file objects, especially if they'll
all be joined into a common access path anyway....

If you need to access this monster file via SQL, it's important to ensure
that you have the correct indexes already built.  Performance tuning in SQL
is sometimes a bit like sorcery or alchemy...  You might see what you want
today, but tomorrow it won't work the same....

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Douglas W. Palme
Sent: Wednesday, February 01, 2006 8:08 AM
To: RPG Group
Subject: Chaining with a very large file


we may be faced with having to allow an interactive program to do a chain to

a very large file; one with approximately 1.1 billion records and a file 
size of approximately 9.7gb of disk space.

Are there any performance issues that I should take into consideration?  
Should I consider breaking the data down into multiple files? 

The file will have a total of three numeric fields, all packed, 5 digits for

the first two and 4 digits for the third.

Suggestions, thoughts, helpful hints.....would all be appreciated.


If you bought it, it was hauled by a truck - somewhere, sometime.