× 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.



Here's another possibility that might fit if the circumstances are right.   
 
Put the data and a few of the logicals in another library named perhaps...
History????  Then create a duplicate object in the original library, leaving
it empty of course, and add of all the  logicals to it..
 
When you need to read or update a record, look in the new file first.  If
not there, look into the historical file and copy it to the new file. Update
only the new file.  If its a delete, delete in both files.  If an add, add
just to the new file.
 
Since no changes or adds are happening in the historical file, a reorg never
needs to be done except to recover space.  
 
Thusly, all records are available, but the 80/20 rule means the unused,
undeleted records will not be in the new file and should provide over time a
small,  fast file.  After a few months one might expect substantial
improvements in performance.  In the beginning it'd be at least as fast  as
the days before a reorg, and very soon it would become lightening fast.
 
Implementation might need triggers and careful thought of which logicals to
place on the historical file.  LPAR sounds like an ideal fit here, too.   
 
While an expensive solution this might be cheaper than members.  Members are
a mine field, and a wonderful solution that went nowhere  -  like Betamax.
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: Friday, May 09, 2003 03:35:32
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Re: Physical File Performance
 
The main reasons for the reorgs are.
A. To remove the large number of deleted records.
B. To hopefully improve the performance
C. To reclaim some space.
D. To highlight the problem of large files to our software supplier !!
E. This file is an integral part of our system; it alone represents 50% of
our total database. For this reason we like to keep an eye on it.
 
Yes the file is keyed.
 
Noel Johnston 
FBD Insurance plc 
FBD House 
Bluebell 
Dublin 12. 
Ireland. 
PH: 00 353 1 4093200 
FAX:00 353 1 4783574 
DDI: 00 353 1 4093381 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.