Copying from PD to PY

echeng

Active Member
What is the proper way of duplicating PD7333 to PY7333.

We are running AS400 and I copied the library PRODDTA and PRODCTL to CRPDTA and CRPCTL, but some of the tables have missing information. Did I miss some other libraries.
 
You don't want to do that! We tried that, and we had to reload PY from tape. Couple questions:
1) Are there any ESUs, Updates, etc in PY that are not in PD?
2) Any modifications to PY that are not in PD?

We had this situation so what we did was to copy the files from PD that had records, and were not related to what we were testing.

I.e. all ACCT & Purch files, then merged system files.

Good luck.
 
1. No, the ESU, updates, etc are the same in PY and PD
2. Some mod are in PY but not in PD
 
You have to change the SIPATHCD in the F983051 table. It will still have PD.
You will also need to run R989861 to update the object librarian records for
PY.
 
First of all:
Did you only wanted the data set? by the looks of it yes.
or did you also wanted the programms and versions?

If you wanted only the data set than it could or should have been okay.
Did you first delete the old CRPCTL and CRPDTA libs?

We however first delete CRPCTL and CRPDTA and then restore PRODDTA and PRODCTL from tape. Works fine for us.
 
Thanks.

What do I need to do if I want to copy the customized reports and versions.
 
strnage, if all being equal a direct library copy should of work. Try do a manual copy of the missing file records and see what happens.
 
The proper way to copy an environment is to follow the document on the KG for copying an environment. In this case OTI-02-0060 "AS/400 (Non-Coexistent) - Creating a Mirror Image of the CRP Environment for the PROD Environment. "

Modify the instructions to make it PD7333-->PY7333 and you're in business.
 
This requires that you copy the Central Objects and Versions libraries. On
the AS/400 that would be the COPD7333 (Central Objects) and PD7333DNT
(Versions). After doing this you will need to change the SIPATHCD column in
the F983051 table because it will still show PD7333. You will need to change
that to PY7333. Then you will need to run the R989861 to update the new PY
objects in the object librarian.
 
I think it may be safer to rename CRPCTL and CRPDTA, restore PRODDTA and
PRODCTL from whichever media it is held on and then, once proving the copy
successful, deleting the renamed CRPCTL and CRPDTA.


Sid Perkins
Independent Consultant
Tel: +44 1304 825003
Mobile: +44 7713158807
[email protected]
[email protected]

----- Original Message -----
From: "RStam" <[email protected]>
To: <[email protected]>
Sent: 07 November 2002 15:17
Subject: Re: Copying from PD to PY


did you also wanted the programms and versions?If you wanted only the data
set than it could or should have been okay.Did you first delete the old
CRPCTL and CRPDTA libs?We however first delete CRPCTL and CRPDTA and then
restore PRODDTA and PRODCTL from tape. Works fine for us.
NT/W2K Fat Clients
 
For data copy your Proddta and Prodctl libararies (and Prodcom if you use
co-existance). I always restore this from backup so there are no problems
with object locks. Note: it wont restore your SQL packages so the number of
objects in the library will be lower.

If you want to refresh objects then you need to copy Cental objects and
Batch versions.

Cheers
Kieran



echeng
<echeng@riocan. To: [email protected]
com> cc:
Sent by: Subject: Copying from PD to PY
owner-jdelist@j
delist.com


08/11/2002
02:58
Please respond
to jdelist






What is the proper way of duplicating PD7333 to PY7333.

We are running AS400 and I copied the library PRODDTA and PRODCTL to CRPDTA
and CRPCTL, but some of the tables have missing information. Did I miss
some other libraries.
Xe with SP 14.1
AS400, 2 Window2000 Application Servers
Citrix MetaFrame with VPN
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=44780
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+



CONFIDENTIALITY : This e-mail and any attachments are confidential and may be
privileged. If you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.



AS400 V4R5, Win2000, Xe Sp17.1
 
if you know which reports and versions are modified that you want to be put to py then you could transfer them if it are not many reports/versions.
 
Did you clear the CRP libraries before copying the PROD to CRP? A CPYLIB will not replace data in existing data files. And if you SAVE/RESTORE and some of the files have different attributes, you get garbage. I use CPYLIB specifically for the purpose of not copying over existing data files. First I clear the TO LIB, then I create empty F0911, F0411, F0311, F0902 files in the TO LIB. Then I do the CPYLIB, then I use CPYF to copy a smaller set data for the files listed above.

Use the document that was given to make sure you get libraries copied for all of the data sources. Or use this cheat sheet.
 

Attachments

  • 44854-Cloneing Prod to DEV III.doc
    37 KB · Views: 122
Back
Top