Re: Looking for a faster CPYF

At least in the 'old days' copying files with all the LFs active was MUCH
slower as all the paths had to be dynamically updated with each record.
Without them there CPYF gets the data over as fast as I/O allows and
building each access path one at a time is also much faster than
dynamically maintaining a whole bunch of them. As to where the work runs,
I believe that when you do the ADDLFM to cause the system to build the AP
it runs in your job. I don't believe the QDBSRV guys handle the builds
when you do CRTLF or ADDLFM.

- Larry

Larry Bolhuis IBM Certified Advanced Technical Expert:
Vice President System i Solutions
Arbor Solutions, Inc. IBM Certified Systems Expert:
1345 Monroe NW Suite 259 System i Technical Design and Implementation
V6R1
Grand Rapids, MI 49505
(616) 451-2500
(616) 451-2571 - Fax
(616) 260-4746 - Cell

If you can read this, thank a teacher....and since it's in English,
thank a soldier.




rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/05/2009 10:51 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Looking for a faster CPYF






<snip>
automatically removing LF members for the copy and readding afterwards.
</snip>
Is this truly faster? So, sure, the CPYF command may be done but are the
logicals unusable for a long period afterwards because there are system
tasks like QDBSRV.. at the bottom of the WRKACTJOB rebuilding the indexes?


Rob Berendt