|
On Thursday 23 October 2003 21:15, William Washington III wrote: > 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. I *think* I've seen a difference depending on whether the TOLIB already exists. It's just using CRTDUPOBJ under the covers, from what I understand, and maybe it's using DATA(*YES) for CRTLIB(*YES) & DATA(*NO) for CRTLIB(*NO). Haven't used it often enough (or recently, for that matter) to tell for sure. > 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! Well, you *could* use my free test environment tools to do the work for you ;) They can create a test library, then create a copy of any referenced files, etc from target program(s). Data can be copied across by scripts that can do straight CPYFs, or built in SQL to get subsets of data. http://www.dbg400.net/dbg400.html for details & code download. Regards, Martin -- martin@xxxxxxxxxx AIM/Gaim: DBG400dotNet http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news / \
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.