|
Michael, If the unique key is giving a lot of overhead during the coversion with CPYF, there is a tricky alternative. You can remove the access path from the PF with RMVPFCST KEEP(*NO), IIRC. After the conversion is conpleted, you can add the access path with ADDPFCST. Just a thought. Regards, Carel Teijgeler. *********** REPLY SEPARATOR *********** On 11-11-02 at 14:36 Mlpolutta@aol.com wrote: >-- >[ Picked text/plain from multipart/alternative ] >Hello folks, > >Our product has a main file (with a unique key on the PF, plus a LOT of >logical files) that can grow to pretty large record volume (25M to 200M >records). We are needing to change the way we do a new release with a >database change to that file. The question I have is this - what is the >best >way to update the database file definition and translate the data to the >new >definition for a large record count? > >CHGPF changes the file "serially" which is terribly slow. I have written a >process that submits a given number of "parallel" CPYF commands, but it >appears that the constraint is in building the UNIQUE access path of the >PF. >Once I get to 5 or 6 jobs for a 3.5M record test data set on our >two-processor development box, I cease to get runtime improvement. It >takes >1:20 plus/minus 3 minutes. (an hour and 20 minutes) I have removed all >logical files so that the only index being built is the UNIQUE one on the >physical file. > >I hope the question is clear. What do you folks think? > >Thanks in advance, >Michael Polutta >Atlanta, GA >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l.
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.