|
I did mean using SELECT in the DDS. As far as a stigma, it really depends on who you speak with. I think if done correctly, doing this type of selection at the micro code level (in DB2) is more efficient. Also, this LF I am thinking of will be used in multiple programs so it is not a single purpose need. Thanks -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com] On Behalf Of boothm@earth.goddard.edu Sent: Thursday, December 16, 1999 12:56 AM To: MIDRANGE-L@midrange.com Subject: RE: file merge dilemma I am curious how you mean "or using a SELECT in DDS to only look at certain records." Will you be using the SELECT in the DDS for the logical file? Or did you mean a dynamic selection in a DDS display screen in the program? Frankly, writing a few lines of standard RPG code strikes me as being a lot better choice than building another Logical File and all of it's associated overhead. In fact, I'd probably even rather create the needed file with CL and OPNQRYF, doing the "select GreaterEqual" and "select certain" process in the CL instead of building another logical. But then, maybe building logicals freely may be the new way? Is there no longer the stigma there once was against building a logical for one single-purpose program? _______________________ Booth Martin boothm@earth.goddard.edu http://www.spy.net/~booth _______________________ "Sam Kanakanui" <kanakanuis@mindspring.com> Sent by: owner-midrange-l@midrange.com 12/15/1999 11:57 PM Please respond to MIDRANGE-L To: <MIDRANGE-L@midrange.com> cc: Subject: RE: file merge dilemma <groan> Matching records? Hmmm... Actually that won't work because I need to read this combined file either w/SETLL or using a SELECT in DDS to only look at certain records. Thanks anyway. -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com] On Behalf Of boothm@earth.goddard.edu Sent: Wednesday, December 15, 1999 9:25 PM To: MIDRANGE-L@midrange.com Subject: Re: file merge dilemma You don't mention using RPG. If you are using RPG then use InputPrimary and InputSecondary with M1 - M4 on the keys if the records are being processed in key sequence. Its easy, fast, and accurate. _______________________ Booth Martin boothm@earth.goddard.edu http://www.spy.net/~booth _______________________ "Sam Kanakanui" <kanakanuis@mindspring.com> Sent by: owner-midrange-l@midrange.com 12/15/1999 08:46 PM Please respond to MIDRANGE-L To: <midrange-l@midrange.com> cc: Subject: file merge dilema I'm sure the answer to my problem is easy but I'm not seeing it. I have a need to join 2 PFs and process them as 1. They are identical in record format name, field names and characterisitics. They both have the same four fields defined as a key. If you put the records from both files together you would still have a unique key. I have been reading about join LFs but I don't see an example of this scenario so I am not sure if I can use that within DB2. I know I can copy the 2 files into 1 every time I want to process the merged files but of course, that's a lot of overhead. Does anyone have an idea? TIA Sam Kanakanui Borg Systems Inc. +--- | 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.