|
On my system the default value for CRTDUPOBJ is DATA(*NO). CPYLIB still copies the data. -----Original Message----- From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Thursday, October 23, 2003 6:48 PM To: Midrange Systems Technical Discussion Subject: Re: CPYLIB and no records copied William, see what the command default is now for CRTDUPOBJ on the DATA() parameter - I know that PDM knows to make it *YES for PFs, but maybe CPYLIB does not. You could CHGCMDDFT for the duration, if need be. Vern At 03:59 PM 10/23/2003 -0700, you wrote: >Hi Andy, > >I am not aware of any ASP consideration I amviolating here. I do have >database triggers on the files in question. But I had them in past runs >of this procedure. I make sure that I remove all triggers after I've >copied the files into the test library (because I don't need the >functionality of the triggers in the test environment.) > >My CL program clears the target (test) library, then copies all objects >from one library to the other. It's almost like I'm doing a CRTDUPOBJ >with DATA(*NO). Very frustrating! > >If I have to, I can programmatically determine the physical files in the >"from" library and do a CRTDUPOBJ or CPYF with MBROPT(*REPLACE), but I >know I didn't have to do this last year... > >Ideas?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.