and a requirement for stronger administration skills.
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.
-- 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. Verifywith
> your Vendors that their apps are 7.1 compliant and run the Anzobjcnvwon't
> process until it is clean or you completely understand what will or
> convert to 7.1 and if it won't, can you abandon that program/app or doyou
> need to replace / upgrade it either before or just after the upgrade.very
> 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
> careful plan and care so you don't down level OS objects in places likeand
> 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
> leave crap behind you don't need any more. #2 You be able to get to theshorter
> point of refreshing your data files to go live, This should be much
> downtime in theory than Upgrade to 7.1 and then later Save/Restore 21 toWaters<bwaters@xxxxxxxxxxxxxxxxxx>wrote:
> move the the new box.
> On Wed, Oct 31, 2012 at 8:53 AM, Billy
>> > We are in the planning stage of migrating from V5r4 to V7.x loaded
testing>> > new server. Is anyone willing to share their time line related to
"cutover" over>> > this process? My boss is under the impression we can do this
in>> > the weekend without any prior testing on the new server / OS. Thanks
-->> > advance for your assistance.
>> > Billy Waters
>> > --
This mailing list archive is Copyright 1997-2013 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