Good suggestion. But with all the security and authority issues
these days - and prod running on different h/w that developers don't
even have access to - is there an easy way to ensure that the new
file has EXACTLY the same authority and security attributes as the
old one? Does CRTDUPOBJ supply all the necessary duplication?
With CPYF, I know for sure that the data is ending up where it came
Jon Paris on Wednesday, January 23, 2013 5:04 PM wrote:
On 23 Jan 2013 11:25, Stone, Joel wrote:
Can this be done in one SQL statement with the result placed
back in WORKFILE1?
Or should I create a new table QTEMP/WORKFILE2 using DISTINCT or
GROUP BY, and then CPYF back to WORKFILE1.
Another option being to create a new file delete the old one and
either move or rename the new one to the old name. Neither move or
rename would actually move the data so both should be more
efficient than copying the new on back again.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact