× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: file merge dilemma
  • From: "Mark Walter" <mwalter@xxxxxxxxxx>
  • Date: Thu, 16 Dec 1999 16:26:56 -0500

All right!!! Someone actually still uses the cycle. I'm glad I'm not the
only one.
----- Original Message -----
From: <boothm@earth.goddard.edu>
To: <MIDRANGE-L@midrange.com>
Sent: Wednesday, December 15, 1999 9:25 PM
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
> +---
>

+---
| 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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.