MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » November 2012

RE: V5r4 Upgrade



fixed

While it is an easy upgrade/migration that I do all the time, I would highly recommend the two stage approach when a older machine can be upgraded to the same release as the new machine. First, this offers two benefits. You are only changing one thing at a time (Upgrade first from V5R4 to 7.1), and secondly the migration from a 7.1 machine to a 7.1 machine is a MUCH easier migration.

Now, a smart person can use the new box to "test" their software at the new release and then just clear the box out and get ready for the live migration. Initialize the new machine by loading JUST Lic ( Put the 7.1 I_BASE_01 into the DVD, do a D Manual IPL) when loading the LIC make sure you take option 2. Then load just the OS, also at 7.1. Now on the current V5R4 box, create a library called RTVSYSINF, and run the command RTVSYSINF with a param of RTVSYSINF. Then do a GO SAVE 21 on your V5R4 machine. On the new box make sure ALWOBJRST is *ALL, JOBMSGQ is *WRAP, and JOB-message-Q size is 64, Verify Object is set to 1, and FRCOBJRST is set to no. Next take the tape to the new box (which just has OS & LIC), and restore User profiles, then restore Config, Restore *NONSYS, restore DLO, and then Restore the IFS. Run UPDSYSINF with a parm of RTVSYSINF from Everything is currently at a mixed mode, but that is ok. Run a Restore Authority, followed by a Restore DLO. Now, upgrade all the LPPs to 7.1, apply the PTFs and IPL the machine. Now run STROBJCVN on all your program libraries and you are ready to go.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, November 01, 2012 8:40 AM
To: Midrange Systems Technical Discussion
Subject: Re: V5r4 Upgrade

I agree, that for some of these people who only upgrade once every 7-10 years that it might be best to farm this out. Of course, if they think they'd rather spend the money on getting an HMC versus paying someone to farm this out to, that's their choice.


If they want to tackle it themselves the big clue is IBM calls this a data migration and documents the process of moving from one system running V5R4 to a new system running 7.1 at http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzamc/rzamc1.htm


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 11/01/2012 08:22 AM
Subject: Re: V5r4 Upgrade
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Rob,

You'll argue that Larry, Pete, and I do this all the time (as well as
several others on the list that regularly contribute) so it's simple to
us. True, but it's not all that advanced. If your unsure about the
system administration bits, get some help for a couple of days. It's
well worth the investment, and I often get IT Directors to use the
educational funding for it, since I teach the techniques while we do
it. Now the skills stay and you have a well set up system.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 11/1/2012 7:11 AM, rob@xxxxxxxxx wrote:
<snip>
and a requirement for stronger administration skills.
</snip>
is a major reason why I discourage it for those shops that only do this
once ever 7-10 years.

You really have to know what you are doing. It's not a simple matter of
taking MYPGMLIB, MYDTALIB from your V5R4 machine, restoring it on your
7.1
machine and calling it a day. There's so much configuration stored in
both 'traditional' libraries and now in stream files outside of the
/qsys.lib file system.

There's been a few occasions on this list where people have done this
wrong and are still trying to clean up the mess months later.

Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept
1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108
6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Jim
Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx> To: Midrange Systems
Technical Discussion <midrange-l@xxxxxxxxxxxx>, Date: 11/01/2012 07:58
AM Subject: Re: V5r4 Upgrade Sent by: midrange-l-bounces@xxxxxxxxxxxx
If the ability to "re-implement" your software, meaning move it from
an older box to a new box presents itself, I will most often make that
choice for the very reasons Kirk points out. You can really clean up a
system. Also. you now have the ability to move custom work management,
communications, and configuration objects into a library of your
choice not QGPL, or QUSRSYS. You leave old objects no longer needed
behind. Once the new box has the OS loaded, user profiles,
communications, work management set up, ect. without the applications
and data on it, you can take a base back up. Take this opportunity to
create your own install media. Now if you ever rebuild the system use
your own install media and most of that will be preset for you! Really
neat if you need to build additional LPARs! There are real advantages
to the what Kirk suggests if you stop and think of them. The downside,
more work initially and a requirement for stronger administration
skills. The payoff in the end is much higher than the cost in my
experience. Jim Oberholtzer Chief Technical Architect Agile Technology
Architects On 10/31/2012 5:07 PM, Kirk Goins wrote:
Plan, Plan and More Planning as the others have basically said.
Verify
with
your Vendors that their apps are 7.1 compliant and run the Anzobjcnv
process until it is clean or you completely understand what will or
won't
convert to 7.1 and if it won't, can you abandon that program/app or
do
you
need to replace / upgrade it either before or just after the
upgrade.

Upgrading the Old system to 7.1 has its risks, but they are
manageable.
Leaving the 5.4 box alone and moving everything to the 7.1 also
needs
very
careful plan and care so you don't down level OS objects in places
like
QGPL, QUSRSYS etec as well as the IFS. 2 advantages I see of
'moving
things' to the new box and not up grading. #1 Great time to Clean
House
and
leave crap behind you don't need any more. #2 You be able to get to
the
point of refreshing your data files to go live, This should be much
shorter
downtime in theory than Upgrade to 7.1 and then later Save/Restore
21 to
move the the new box.

On Wed, Oct 31, 2012 at 8:53 AM, Billy
Waters<bwaters@xxxxxxxxxxxxxxxxxx>wrote:

> We are in the planning stage of migrating from V5r4 to V7.x
loaded
to a
> new server. Is anyone willing to share their time line
related to
testing
> this process? My boss is under the impression we can do this
"cutover" over
> the weekend without any prior testing on the new server /
OS. Thanks
in
> advance for your assistance.
> Billy Waters
>
> --
--





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact