Dan, 

     Make the *PF seq and put any keys into *LF ect..files.  When you are 
ready to load the file remove all the *LFM's and when you have the data 
cleaned up then run a job with the ADDLFM function, or *JF as needed.  

        JMS

On Mon, 20 Jul 1998, Dan Rasch wrote:

> 
> I am in the middle of a large conversion, where during the 'big bang' - we
> will encounter numerous duplicate keys.  The data comes from a mainframe,
> and making the file truly unique first would probably be as large a task
> as the conversion itself.
> 
> My question regards the nature of the I/O involved for a duplicate key.
> Is there a way to reduce the processor time the machine uses to determine
> a duplicate key exists?  We looked at the file description, and nothing
> was obvious.  The language is COBOL, and rewriting the code is less tahn
> desirable (although I personally feel a START in the proper paragraph
> would do wonders)....... 
> 
> Dan Rasch - because if the human species concentrated on the really 
> important things in life, there would be a shortage of fishing poles!
> 
> 
> +---
> | 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 thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].