|
Thanks for confirming my suspensions. Great tool but poor implementation IMO. Christopher K. Bipes mailto:ChrisB@Cross-Check.com Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 If consistency is the hobgoblin of little minds, only geniuses work here. Karen Herbelin - Readers Digest 3/2000 -----Original Message----- From: Rich Duzenbury [mailto:rduz@westernmidrange.com] Sent: Monday, March 27, 2000 1:10 PM To: RPG400-L@midrange.com Subject: EOF Delay (was RE: Changing triggers) I can try. Using EOF delay (AFAIK) really only works for addition of new records literally past the current end of file. I don't think it works for keyed updates, and I'm pretty sure inserting at a record number lower than the record number at end of file (in the case of RRN access in a reusedlt(*yes) situation) probably won't cause the read statement to get the record. I know it's really a long URL, but here's the search I did for EOFDLY, jumping to the appropriate discussion: http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QB3AUC01/2.3.2.3?ACTION= MATCHES&REQUEST=EOFDLY&TYPE=FUZZY&searchTopic=TOPIC&searchText=TEXT&searchIn dex=INDEX&rank=RANK#FIRSTHIT So, when I use it, the file that captures the additions has no keys, and I just ovrdbf somefile eofdly(30) call somerpg And somerpg reads the file processing every record. The operating system takes care to hand the records into the program every 30 seconds. Sometimes it is beneficial to have a logical where the key is set to *NONE, that has a select/omit statement such as recstat *ne 'P' (which means processed in this case). Periodically, I delete all the processed records and reorganize the file. Regards, Rich +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.