|
When you run your copy process, observe CPU usage. If you are close to 100%, I doubt that splitting it in parallel will give you any benefit. On the other hand, if you have more than one procesor on system, this is certainly worth a try. To have benefit from splitting some work to several parallel processes, there should be underutilized system resources you hope to use better. You may also want to look at 5722SS1 option 26 - DB2 Symmetric Multiprocessing. It can process index update in parallel even for one job. But again, to benefit from any sort of parallelism, you first need some unused resourcs to spare. Alexei Pytel "The better is the worst enemy of the good" Dimitri Efimov <defimov@wiese.com. To: MIDRANGE-L@midrange.com pe> cc: Sent by: Subject: RE: How to optimize COPY *ADD owner-midrange-l@mi drange.com 07/27/2001 02:36 PM Please respond to MIDRANGE-L That's correct, we are copying daily built file to history file, the point is - the history file has more than 200 mln. of records, even more - it has 18 index files. So it's impossible to find "keyed sequence". But I'm going to try the solution Buck's solution ("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) ...) hope it will work. Thanks a lot Dmitri Efimov Banco Wiese Sudameris DEF -----Mensaje original----- De: Joel Fritz [mailto:JFritz@sharperimage.com] Enviado el: Viernes, 27 de Julio de 2001 01:25 p.m. Para: 'MIDRANGE-L@midrange.com' Asunto: RE: How to optimize COPY *ADD If I understand you correctly, you're copying a file that's built daily to a history file. Six hours sounds like a long time for 4,000,000 records. Are you copying in keyed sequence? If you are you could try fromrcd(1). Otherwise, you could break it down into "simultaneous" submitted jobs using fromrcd(x) torcd(y). +--- | 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-2025 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.