× 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: How to optimize COPY *ADD
  • From: "Peter Dow" <pcdow@xxxxxxxxx>
  • Date: Fri, 27 Jul 2001 12:25:48 -0700

Hi Dmitri,

In addition to Buck's suggestions, you could try changing any non-unique
keyed logical files to MAINT(*REBLD) before the CPYF, then MAINT(*IMMED)
afterwards.  Or simply remove the logical file members from all related
logical files and add them back afterwards.

hth,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax

From: "Buck Calabro" <Buck.Calabro@commsoft.net>


> Dmitri E wrote:
> >We use to make copy - add to historical file (PF + 18 LFs)
> >daily. That means to copy 4000000 records, which takes
> >about 6 hours using normal CPYF command.
>
> Several thoughts:
> 1) On the CPYF, try FROMRCD(1).  This will tell CPYF to read the source
file
> in sequential order rather than by key.
> 2) Multiple CPYF commands in parallel might be better if you have a good
way
> to partition the records such as FROMRCD(1)
> TORCD(1000000)...FROMRCD(1000001) TORCD(2000000) and so on.
> 3) If the application allows it, put a trigger on the transaction file to
> copy each record to the history file as they are added to the transaction
> file.  Then the index update load is spread through the entire day instead
> of all at once.
> 4) Along the same lines, perform the CPYF many times throughout the day
> instead of once.



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.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 ...

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.