Ansicht
Dokumentation
09656 - Antwort: Moving 4.0B systems
General Data in Customer Master SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Antwort: Moving 4.0B systems
Hi Robert,
alway when I have to do somthing like that I use the homogenous system
copie procedure from SAP. But we are runnig 4.6C.
We use the origianl CD's and if there are problems during the installation
with the kernel, we apply the new one.
Best regards
Thomas
|---------+---------------------------->
| | Robert Clay |
| | <zreclayZconsolut.co|
| | m> |
| | |
| | 18.03.2003 16:06 |
| | Bitte antworten |
| | an SAP on System i |
|---------+---------------------------->
>-------------------------------------------------------------------------------\
-------------------------------------------------------------------|
|
|
| An: DoNotReply@consolut.eu
|
| Kopie:
|
| Thema: Moving 4.0B systems
|
>-------------------------------------------------------------------------------\
-------------------------------------------------------------------|
We are running SAP 4.0B, kernel patch 958 on iSeries V5R1. We have our
production (PRD) instance on one machine and our development (TST) and test
(QAS) instance on another.
When we first implemented SAP, we had all three instances on the PRD
machine. DASD usage was an issue at the time and a decision was made to
move TST and QAS to the other machine. We had consultants that performed
this move.
We are preparing for an upgrade to the latest version of SAP. We only use
FI and CO.
Now, the time has come for the TST and QAS instances to move back to the
PRD machine. I feel certain that I can do this but I want to have an
action plan before I start.
My question concerns whether to treat the movement of the TST and QAS
instances as if they were copies or as if they were new installs (and yes,
I remember the license keys issue). Since we are at 4.0B, the installation
CD and the Installation guide are very dated. In fact, we are now using
the 40B_COM kernel and I do not know how that will impact the process.
Basically, I could either use the LODRUN command and cancel at the
appropriate point and restore the saved R3TSTDATA library from there, just
like a refresh,
***OR***
I could use the CREATE COLLECTION R3<sid>DATA command and just restore the
data library and the kernel library and treat it as a restore, handling the
IFS connectivity and TMS rebuild manually.
Since PRD is already on the machine, couldn't I simply use ADDR3SYS command
and avoid all the drama associated wth the ancient CD and LODRUN?
If anyone has been through a similar situation, any advice and/or insight
would be greatly appreciated.
Robert Clay
Opinions expressed are my own and not necessarily those of my employer.
---------------------------------
Do you consolut?
consolut Platinum - Watch CBS' NCAA March Madness, live on your desktop!
[Non-text portions of this message have been removed]
Y
a
h
o
o
!
G
r
o
u
p
s
S
p
o
n
s
o
r
A
D
V
E
R
T
I
S
E
M
E
N
T
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Durban Tours - Südafrika Safari
ABAP Short Reference RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 4229 Date: 20240426 Time: 054520 sap01-206 ( 2 ms )
