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?

 
------------------------------

message: 10
date: Thu, 23 Oct 2003 17:27:41 -0400
from: "Andy Nolen-Parkhouse" 
subject: RE: CPYLIB and no records copied

William,

I'm not aware of any changes. There are some restrictions related to
copying a library from one ASP to another. Are you doing this by any
chance?

Regards,
Andy Nolen-Parkhouse

> On Behalf Of William Washington III
> Subject: CPYLIB and no records copied
> 
> Hello all,
> 
> Has anyone noticed a change in the CPYLIB command? Last year, I would
> clear my test library, then do a CPYLIB FROMLIB(production) TOLIB(test)
> CRTLIB(*NO) to refresh my test library with new data.
> 
> Now, it seems that all of the files are brought over, but they have zero
> data records!
> 
> I'd hate to think I'll have to individually copy files from prodcution to
> test. Tell me I'm wrong!
> 
> William

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.