Re: Upgrading/Migrating from V4R5 to V5R4M5

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Nick,

At first glance...it doesn't appear to be a workable plan.  Perhaps
it's simply a terminology mixup....

Here's how I would do this
1) Save option 21 on the 270 at v5r4m5 (optional, only if you want to
put the 270 back)
2) Save option 21 on the 620 at v4r5
3) Scratch install the save from the 620 onto the 270, this will load
v4r5 onto the 270 use the "Recovering your entire system after a
complete system loss – Checklist 17" in the backup and restore manual.
(http://publib.boulder.ibm.com/pubs/pdfs/as400/V4R5PDF/C4153044.PDF)
4) Upgrade the 270 from v4r5 to v5r2
5) Save option 21 on the 270 at v5r2 (optional, as a backup)
6) Upgrade the 270 from v5r2 to v5r4m5
7) Save option 21 on the 270 at v5r4m5
8) Restore the 270 tape @ v5r4m5 onto the 810 use the "Recovering your
entire system after a complete system loss–Checklist 20" in the v5r4
backup and restore Manual.

Details procedures from moving data from one system to another are found in the
v4r5 "Risc to Risc Roadmap"
http://publib.boulder.ibm.com/pubs/pdfs/as400/V4R5PDF/A4151554.PDF
v5r4 "Data migrations"
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzamc/rzamc.pdf

Note: If the 620 is faster (both CPU and disk) than the 270, it might
save you some time if you performed the v4r5 to v5r2 upgrade on the
620 instead of the 270.  In which case you'll need the
v5r2 backup and recovery manual
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/c4153046.pdf
v5r3 Data migration
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/rzamc/rzamc.pdf


HTH,
Charles Wilt


On Mon, Aug 2, 2010 at 10:38 AM,  <Nick_Radich@xxxxxxxxxxxxxx> wrote:
> Happy Monday!
>
> We are finally moving from our 620 to an 810.  Getting a little closer to
> the 21st Century:-)
>
> IBM is coming today to setup the 810.
>
> Coming from V4R5 and going to end up at V5R4M5 on the 810.  We are not
> going to go past V5R4M5 because of the modifications we have made to our
> ERP software, MAPICS, and I am a 1 person shop.
>
> We have another box, a 270, to use an intermediary step.
>
> I know we can't go up more than 2 levels, so we are going to use the 270
> as a go between.
>
> The 270 is at V5R4M5 already, but I would like to bring it down to V5R2 so
> I can restore my 620 onto it in one step.
>
> The overall/tentative/high level plan I have is this:
> 1)      Do a GO SAVE 21 on the 270, to save the V5R4M5 version
> 2)      Bring the 270 down to V5R2
> 3)      Restore everything I have on the 620 to the 270, to get all of my
> Security, Subsystems, OUTQs, etc. there.  I have a GO SAVE 21 for this.
> 4)      Do a GO SAVE 21 on the 270
> 5)      Restore from the 270 to the 810, just the 'System'  stuff,
> Security, OUTQs, Subsystems, etc..
> 6)      Restore V5R4M5 on the 270
> 7)      Save all of my application software on the 620
> 8)      Restore application software on the 810
>
>
> Does this sound like it would work?
>
> Would restoring my GO SAVE 21 on the 620 onto the 270 bring the 270 down
> to V5R2?  If not, I have CDs for V5R2.  How do I apply them?
>
> It has been 200,000,000 million years since I have done anything like
> this, so I am a little rusty on the System Admin/PTF/OS stuff.
>
> Any advice/help/tidbits would be appreciated.
>
>
>
>
> Thanx,
>
> Nick
>
>
>
> Nick Radich
> Sr. Programmer/Analyst
> EPC Molding, Inc.
> Direct  (320) 679-6683
> Toll free  (800) 388-2155  ext. 6683
> Fax  (320) 679-4516
> nick_radich@xxxxxxxxxxxxxx
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.