Re: CPYLIB and no records copied

Vern,

That's not it - at least judging by my testing.

The only think alluding to that is that, on the help for CPYLIB, a lot of 
the restrictions imposed by CRTDUPOBJ are there.



Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/23/2003 06:47 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


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

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?


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
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.