|
All -list
We were having difficulties when refreshing data libraries in our test
environments due to the long time it was taking to rebuild the logical
files
over the physical files.
I determined that it was much more efficient to first /remove/ the LF
members from the logical files in the to-library /before/ doing the CPYF
command, then submitting jobs to add back the LF members once the PF was
copied - thus was born a new command I call FASTCPYF.
The underlying CPP for this command does the following:
1) DSPDBR of the PF in the to-library to an outfile to capture all of the
logical files that are dependent on the PF in the to-library
2) DSPFD of the PF in the to-library TYPE(*TRG) to an outfile to capture
any
triggers on the file in the to-library
3) Removes all of the LF members from the PF in the to-library
4) Removes all of the triggers from the PF in the to-library
5) Uses CPYF to copy the from-file to the to-file
6) Using the information from DSPDBR, submits jobs to add back all of the
logical file members to the PF in the to-library
7) Using the information from DSPFD TYPE(*TRG), adds back all of the
triggers to the PF in the to-library
Have I missed anything?
From my preliminary testing on a physical file that has a lot of logicalfiles, FASTCPYF can be 10 times faster than CPYF...
- sjl
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
No virus found in this incoming message.
Checked by AVG.
Version: 8.0.101 / Virus Database: 270.9.2/1782 - Release Date: 11-11-2008
19:32
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.