RE: CPYLIB and no records copied

[Jim Damato <jdamato@xxxxxxxxxxxxxxxxx>]

Are there any messages in the job log after the CPYLIB?

Does your CL clear the target library use CLRLIB or some other technique?

Perform a DSPOBJD on a file in the target library.  Was the file really
deleted and re-created or does it have an older create date?

Do you really have any records in production?  :)

-Jim

-----Original Message-----
From: William Washington III [mailto:w.washington3@xxxxxxxxxxxxx]
Sent: Thursday, October 23, 2003 5:59 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CPYLIB and no records copied


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?