Re: CPYF vs. CRTDUPOBJ

[CRPence <CRPbottle@xxxxxxxxx>]

James H. H. Lampert wrote:
> Chris Bipes wrote:
> > CRTDUPOBJ I believe will carry across triggers and other
> > restrictions that you may not want on the QTEMP version.
> > CRTDUPOBJ can be faster if there are many records in the
> > file. You can specify NBRRCDS
> > on the CPYF command as 1 to speed up the process.

  The CRTDUPOBJ with DATA(*NO) would be faster given TRG(*NO) 
CST(*NO) to avoid the other noted concern.  First it would not copy 
any data, and then there would be no CLRPFM to rid of the nuisance 
record that might have resulted from the CPYF.

> Would if it accepted zero for NBRRCDS, given that the
> preferred result would be a completely empty copy of the
> file.

  Zero records can be done by trickery, using FROMRCD(4294967288) 
TORCD(4294967288); i.e. specifying the maximum row number. 
Obviously this /assumes/ the file has never reached the absolute 
maximum.  Similar tricks with keyed selection or data selection can 
be used with similar assumptions about the data.

  I recall recommending NBRRCDS() support zero for that same 
reason, but internal suggestions had no weight.  Only a customer 
submitted DCR would suggest merit for that capability.  I probably 
should have made that change last time I fixed something in CPYF. :-)

Regards, Chuck