|
Jigna, If I understand your logic, your subfile handling is not the problem. The basic concept of loading a page at a time, letting the program only handle page down, extending the subfile, is solid and efficient. I am assuming that after you write five subfile records, you write the subfile control ecord and display the subfile. this should only require five reads of the customer master. A page down (*IN85) would require another five reads. (Assuming you maintained your position in the master file, otherwise, an extra I/O to get to the customer record for the last record displayed, then read to the next one.) I do not understand what having millions of records in the customer master has to do with your problem. BTW, you can only load 9999 records in a subfile. Bob jigna desai wrote: > Hi all, > i have a situation with a subfile pgm where the SUBSIZ is 6 & SUBPAG > is 5 .Indicator 85 is rolldown indicator & 84 is rollup.Records r > read,written & displayed 5 at a time with each subsequent pagedown > which is handled in the pgm via *IN85.Pageup has no logic since after 3 > pagedowns when 20 records r displayed -the previous 15 records r > already in the subfile & need not be accessed again. > However,the problem is our customer record file being very very > large comprising of millions of records > it causes a performance issue since the process is very slow.To handle > pagedown -- i think there is no better method than used in the pgm so > what then, should i do so that the process is not slow ? > +--- | 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-2025 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.