Thanks, Colin. That's the way I like to do a conversion as well.
Jim
Colin Allinson wrote:
This is a multipart message in MIME format.
--=_alternative 004D9A8DC12574F2_=
Content-Type: text/plain; charset="US-ASCII"
Jim Bohnsack <[EMAIL PROTECTED]> wrote :-
......... I don't like doing "big bang" conversions. I would like
to be able to move the 5.4 level of CP from my 2nd level install system
to my test lpar and then move the 5.4 level of CMS and then the 5.4
level of TCP/IP and some other things. ............
Jim,
We, like you, do not do 'big bang' conversions.
We have upgraded CP to 5.4 on all systems but we still have our main
system running everything else (CMS, TCPIP etc.) at 5.3 level.
We go to a certain amount of effort to ensure that we can run multiple CMS
levels in parallel and swap between them - so the next thing to do is make
CMS 24 available (but not the default).
The next thing we do is uplevel TCPIP (and make sure it is running the
corresponding level of CMS). At the same time we make sure we have the
right level of TCPIP utilities available on our X(319) disk. If we fall
back TCPIP then we must fall these back as well. At this stage most users
are still running CMS23.
The next stage is to get some users to swap to CMS24 (using our SWAPCMS
utility) - or configure them as CMS24 by default.
This is the process we always use and this is where we are right now on
all but one system (on that we have not upgraded TCPIP yet). It has never
given us any problems.
Colin Allinson
Amadeus Data Processing GmbH
--=_alternative 004D9A8DC12574F2_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=1 face="sans-serif"><b>Jim Bohnsack <[EMAIL PROTECTED]></b></font><font
size=2 face="sans-serif">
wrote :-</font>
<br>
<br><font size=2 face="sans-serif">> ......... </font><tt><font size=2>I
don't like doing "big bang" conversions. I would like <br>
> to be able to move the 5.4 level of CP from my 2nd level install system
<br>
> to my test lpar and then move the 5.4 level of CMS and then the 5.4
<br>
> level of TCP/IP and some other things. </font></tt><font size=2
face="sans-serif">............</font>
<br>
<br><font size=2 face="sans-serif">Jim,</font>
<br>
<br><font size=2 face="sans-serif">We, like you, do not do 'big bang'
conversions.</font>
<br>
<br><font size=2 face="sans-serif">We have upgraded CP to 5.4 on all systems
but we still have our main system running everything else (CMS, TCPIP etc.)
at 5.3 level.</font>
<br>
<br><font size=2 face="sans-serif">We go to a certain amount of effort
to ensure that we can run multiple CMS levels in parallel and swap between
them - so the next thing to do is make CMS 24 available (but not the default).
</font>
<br>
<br><font size=2 face="sans-serif">The next thing we do is uplevel TCPIP
(and make sure it is running the corresponding level of CMS). At the same
time we make sure we have the right level of TCPIP utilities available
on our X(319) disk. If we fall back TCPIP then we must fall these back
as well. At this stage most users are still running CMS23. </font>
<br>
<br><font size=2 face="sans-serif">The next stage is to get some users
to swap to CMS24 (using our SWAPCMS utility) - or configure them as CMS24
by default.</font>
<br>
<br><font size=2 face="sans-serif">This is the process we always use and
this is where we are right now on all but one system (on that we have not
upgraded TCPIP yet). It has never given us any problems.</font>
<br>
<br><font size=2 color=#1a61a9 face="Arial"><b><br>
Colin Allinson</b></font><font size=1 face="Arial"><b><br>
</b></font><font size=1 color=#666666 face="Arial"><br>
Amadeus Data Processing GmbH<br>
</font>
--=_alternative 004D9A8DC12574F2_=--
--
Jim Bohnsack
Cornell University
(972) 596-6377 home/office
(972) 342-5823 cell
[EMAIL PROTECTED]
