Re: upgrading from 720 to i520

["Ang, Daniel" <ang@xxxxxxxxxx>]

Hello All:

I'll have a real hands on in two weeks time in moving from 720 from 
i520. I've upgraded 720 to be running v5r3 and everything is running 
smoothly. Now my question is:

In normal approach, i would do a complete save (option 21) of 720 to a 
tape. Boot from D on the i520 and run the LIC installation, v5r3, 
additional license programs, user profile, ifs, system settings 
restoration, and etc from the tape. Tape is just too slowly at times .. :(

Is there any alternative in doing so without the tape? ObjectConnect 
seems a good alternative but then it would only send lib over, what 
about user profiles and other system settings?

Doing a complete save (option 21) to a savf seems a good idea, but i've 
left 10gb on 720, which is not sufficient. The whole box is around 100gb.


JOberholtzer@xxxxxxxxxxxx wrote:
> Folks:
>
> I believe Larry and I wrote this question.
>
> A: is wrong because the 720 is not at V5R3 yet.  An i520 cannot run
> anything less than V5R3
> B: is the correct answer.
> C: is wrong because there is no upgrade path from a 720 anymore.  Can't do
> it.
> D: is wrong because the objects would not restore properly.  The SLIC would
> not restore and make the machine braindead in a very great hurry.
>
> For those folks who would like to perform an upgrade from a V5R2 or V5R1
> machine without doing the OS upgrade first, it can be done.  Load SLIC and
> i5OS from the CDs.  Do not load QGPL and QUSRSYS.  Restore those from your
> source machine.  Perform a SLIP install of QGPL and QUSRSYS.  You will be
> forced to add Extended Base Support at the same time.  Continue by loading
> the balance of the LPPs from the V5R3 media.  Restore the balance of the
> user data.  Last Apply Cumulative fixes and groups
>
> CAUTION;  This is not recommended procedure and should not be done by
> someone without the knowledge and experience to pull it off, but it can be
> done.  There are just too many places stuff can go wrong in this process.
> If you have BRMS in the mix, it gets more complicated due to database
> changes etc in BRMS.
>
> Jim Oberholtzer
>
>