• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Test Environment

LisaE

Member
Can someone tell me what is the best way to refresh the test environment? In the past, I've always restored the production libraries (*DTA, *COM, *OBJ, *SEC, *SRC) from tape to the test environment. However, there are things missing from the test environment, such as inventory cost information. I have tried clearing the libraries and then restoring as well, with no good results.

Thanks very much.

lisa e
 

Gavin Clark

Active Member
G'Day Lisa

The method you are using to create the test environment sounds like it should work. It might pay to run the DSPDBR (display database relations) command over some of the files you are having trouble with, just to check that the logicals are pointing to where you think they should.

The process I use for creating a test environment on the same machine, is to delete the test data library and then re-create it by submitting a job copying the live data library, using the CPYLIB command. I have assumed that the test environment shares the common object and security libraries, if not then the same process can be used for them. One thing to check is that if your copy of the library is to occur when the live environment is in use, then some files may/will be locked, the test version of these files will have no records, and the records will have to be copied using CPYF command when the CPYLIB job is complete (check the joblog).

Hope this is useful.

Regards

Gavin Clark
-----------

IT Service Provider
World/Oneworld Applications Support
World Development
gavin_clark@usa.net
 

ehassman

Member
Lisa
I sounds like you have some of the logical pointing to the wrong libraries.
The best thing to do is delete all the files from the test environment, Save
the data first, remember to delete the logical before deleting the
physicals.
Recreate the files from a known clean backup, or maybe even JDESRC, and
maybe JDEDTA. Restore the data if possible.
If this does not work you have create the data files again.
Save the environment once you have everything set the right way.
If all fails rebuild everything from JDEDTA, and maybe JDESRC.

Ed Hassman
Ehassman@hotmail.com



>From: LisaE Reply-To: jdeworld@jdelist.com To: jdeworldml@jdelist.com
>Subject: Test Environment Date: Mon, 19 Mar 2001 12:00:57 -0800 (PST)
>
>Can someone tell me what is the best way to refresh the test environment?
>In the past, I've always restored the production libraries (*DTA, *COM,
>*OBJ, *SEC, *SRC) from tape to the test environment. However, there are
>things missing from the test environment, such as inventory cost
>information. I have tried clearing the libraries and then restoring as
>well, with no good results.
>
>Thanks very much.
>
>lisa e
>
>
>-------------------------- Visit the forum to view this thread at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=W&Number=7536
>+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + This is the
>JDEList World Mailing List. Archives and information on how to SUBSCRIBE,
>and UNSUBSCRIBE can be found at http://www.JDELIST.com + - - - - - - - - -
>- - - - - - - - - - - - - - - - - - - - +
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
 

wayne_severson

Active Member
We refresh every other Sunday. We do this during a down time on the
system(no user activity).
What I do is a clrlib on all test libs and then a cpylib from production
libs to test.
This works fairly well for us however you can still miss some objects if JDE
does not have
authority to them or someone inadvertently gets into the system(we end
Qinter to prevent this). The authority issue pertains to custom objects.

You can also get into authority issues by restoring from savlibs.
 

SDurfee

Member
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.........
 

TGreene

Active Member
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

>>> sdurfee@flowcorp.com 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
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
 

RKlaja

Member
-----Original Message-----
From: Celestino Janet
Sent: Thu 3/22/2001 8:54 AM
To: 'jdeworldml@jdelist.com'
Cc:
Subject: RE: Test Environment



Our company purchased the TestBench400 product from The Original
Software Group ( http://www.origsoft.com/) about a year ago. With this
product, we are able to create test environments that are subsets of our
production data. There is some up-front work required to define file
relationships, but once this is done, running subsequent data refreshes
is easy.

-Janet Celestino Leppo
Business Application Developer
NJR Service Corporation
JCelestino@njresources.com <mailto:JCelestino@njresources.com>

-----Original Message-----
From: LisaE [ mailto:thewizard@citlink.net]
Sent: Monday, March 19, 2001 3:01 PM
To: jdeworldml@jdelist.com
Subject: Test Environment

Can someone tell me what is the best way to refresh the test
environment? In the past, I've always restored the production libraries
(*DTA, *COM, *OBJ, *SEC, *SRC) from tape to the test environment.
However, there are things missing from the test environment, such as
inventory cost information. I have tried clearing the libraries and then
restoring as well, with no good results.

Thanks very much.

lisa e


--------------------------
Visit the forum to view this thread at:

http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=W&Numbe
r=7536
<http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=W&Numb
er=7536>
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
 

Nichelle

Well Known Member
After the production data has been copied/restored to the test environment
you should run a WW over F82100 to identify any WW's that create an output
file and change the library designation in the WW version. Otherwise, if
these WW's were to be run in the test environment you could potentially
corrupt production data. If you are talking about restoring programs to a
test environment, to test program changes etc. you must make sure you do not
have any libraries designated in your programs. Such as creating a backup
copy of a file before processing and specifying a backup library. You would
need to change this library designation in the program in the test
environment, otherwise, you could corrupt the production data. If you do
have this situation with libraries being designated in your programs, I have
a solution for you.



Nichelle Wilcox-Furr's Restaurant Group
JDE World A73.11 720 v4r4
 

LisaE

Member
Re: RE: Test Environment

Thanks, everyone for your help. I ended up deleting the test libraries and then restoring from tape. The important thing I found out is that you must have a full backup of the libraries for this to be successful. I also discovered that our production OBJ library was specified in the test library list. This may have caused the problem I was seeing in production. By the way, JDE says there is NO WAY production data could be updated from the test environment.

Lisa
 
Top