|
Don't laugh, one place I was at early in the AS400's "history" was assigned to reduce the (12-hour?) run-time for a program that did some CHAINing to a secondary file for processing. Finally he used MR and cut it way down (hour or two?).. Yeah.. I always had this "deja vu" feeling when all the query stuff starting coming out.. <g> - Alan ----- Original Message ----- From: "Mike Shaw" <mhshaw@xxxxxxxxxxxxxxxx> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> Sent: Friday, May 09, 2003 5:47 PM Subject: RE: Best Way to find duplicate records in same file | Vern, | | And we could go back to matching record processing too! <VBG> | | | | -----Original Message----- | From: midrange-l-bounces@xxxxxxxxxxxx | [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg | Sent: Friday, May 09, 2003 12:55 PM | To: Midrange Systems Technical Discussion | Subject: Re: Best Way to find duplicate records in same file | | Anyone remember control levels? The cycle? Perfect use for it. Put L1 on | | all the fields. If L1 is *OFF, delete the record. Use primary processing | - | not full-procedural. Get a taste of how easy it used to be. | | The "Geezer" strikes again! | | Vern | | At 01:50 PM 5/9/2003 -0500, you wrote: | >I'd pick some logical file, any logical file, for that physical, so | long as | >it included all fields. | > | >I'd define a data structure externally. I'd define a field New data | >Like(The Data Structure) and eval it as equal to the new record.. | > | >Then I would use the key to do setll/read loop while the key is | unchanged. | > | >In the loop if the datastructure equals the new data field, then I'd | process | >my duplicate record subroutine. | > | | | _______________________________________________ | This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing | list | To post a message email: MIDRANGE-L@xxxxxxxxxxxx | To subscribe, unsubscribe, or change list options, | visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l | or email: MIDRANGE-L-request@xxxxxxxxxxxx | Before posting, please take a moment to review the archives | at http://archive.midrange.com/midrange-l. | | | | _______________________________________________ | This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list | To post a message email: MIDRANGE-L@xxxxxxxxxxxx | To subscribe, unsubscribe, or change list options, | visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l | or email: MIDRANGE-L-request@xxxxxxxxxxxx | Before posting, please take a moment to review the archives | at http://archive.midrange.com/midrange-l. |
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.