We have a CL job to refresh test. First it clears the test libraries.
Then it does a CRTDUPOBJ (with NO data) from prod to test for all of the
large detail files (F0911, F0411, F0618, F0619, etc.). Then it does a
CRTDUPOBJ (WITH data) on *ALL files in prod to test. (It will skip the
files that are already there, with a MONMSG). The last step does a CPYF
of selected detail records to the large detail files - like just the
current year, for example. This piece we modify as needed (requires
changing the CL and recompiling). We do create a test version of COMMON
as well. We submit the job to run during the night - submitted from the
AS/400 main menu - NOT from the JDE environment. This works well for us,
but obviously requires an in-house programmer or at least someone
familiar with CL.
Just thought I'd share!
World 7.3 Cum 8
>>>
[email protected] 03/20/01 01:04PM >>>
When we want to refresh our test environment we perform a full save
first (with no one on the system). Once the libraries are on tape we
delete the existing test libraries and restore the production libraries
(RSTLIB) to newly created test libraries. This has worked for us for
many years. Once we have the test libraries in place we begin purging
out some of the older data, since our production library is over 13 gig.
Good luck.........
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=W&Number=7583
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at
http://www.JDELIST.com
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +