|
Booth, Couple of thoughts. Building logical(s) can help. You can do a CHGQRYA QRYTIMLMT(0) and run these reports interactively. When the message comes up take a C to cancel and then look in the job log. If a logical will help there will be a message in the job log telling you what key to build it with. A second thought is that you may be able to put the history records in a history file that is identical to the current file. Then periodically move records that are older than some amount from the current to the history file. You then can create a logical to merge the records together which can be used in programs that need to be able to see all the records such as an inquiry program. Scott Mildenberger > -----Original Message----- > From: booth@martinvt.com [mailto:booth@martinvt.com] > Sent: Thursday, December 21, 2000 9:44 AM > To: midrange-l@midrange.com > Subject: accessing the records in a history file > > > I'd like some insight from folks on this scenario: There is > a history > file of records dating from 1994. Records are added each day and now > there are 3.6 million records in the file. The odds of > anyone going back > to look up something in 1994 are slim but management won't purge any > records. Obviously the newest records are at the end of the > file. All of > the logicals have the customer ID number as the first key. > One logical has > a key of the customer ID and then date and time. > > Each business day there is at least one and sometimes five or > more reports > written for all activity during some recent time period (a > workshift, a > day, a week, whatever). > > This process is becoming a performance pig; additionally > there is a need > for more function. What sorts of suggestions do you people see as > possible enhancements to this? SQLRPGLE? OPNQRYF? a new > Logical on date > and time alone? #GSORT? > > Any suggestions are appreciated. thanks in advance. > > > _______________________ > Booth Martin > Booth@MartinVT.com > http://www.MartinVT.com > _______________________ > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.