Re: Data Migration from a V5R1 model 600 to a V5R4 520

["Jim Franz" <franz400@xxxxxxxxxxxx>]

Chuck,
I would agree a lot can be missing in a data only restore, and my prev post 
was way to simple in the steps outlined. I am leary of unsupported jumps 
(more than 2 releases) and restores of QUSRSYS and QGPL, finding there can 
be trouble with new OS w/old qusrsys config files and old subsystem 
descriptions. I am starting to plan a v4r5 (720) jump to v5r4 (520), and 
half the config on the old box is obsolete remote controllers, frame relay 
cards, and twinax.. It was a surprise when I told them some twinax still in 
use daily (oops).
jim
----- Original Message ----- 
From: "CRPence" <crp@xxxxxxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, August 01, 2007 7:57 PM
Subject: Re: Data Migration from a V5R1 model 600 to a V5R4 520


>   Although restoring only user data might seems acceptable, doing the
> migration ensures some things which were not accounted for in planning
> [e.g. unregistered external stored procedures, distribution queues, job
> schedule entries, etc.] should not end up being an "Oops! I did not
> consider that."  Using a full system restore in that migration can also
> serve as an effective DR test; even if to a different release and only
> the first steps.  With the migration path there is also no concern for
> what of OMIT() and OPTION(*NEW) will not have restored into QGPL &
> QUSRSYS since the full libraries would be restored with the old-release
> objects.data; also ensuring that nobody messes up the system by
> forgetting OPTION(*NEW) and using ALWOBJDIF(*ALL).  RSTCFG, RDBDIRE, and
> System Values are the only things I can think of at the moment [I did
> not review the migration path documentation] which are required to be
> moved/corrected in the migration scenario, and the other noted
> considerations [e.g. directory entries and tcp/ip configurations] should
> be automatically updated as part of [what appears to be to the install
> code for v5r3m0] a supported N+2 upgrade over v5r1m0.
>
> Regards, Chuck
> --
>  All comments provided "as is" with no warranties of any kind
> whatsoever and may not represent positions, strategies, nor views of my
> employer
>
> Evan Harris wrote:
> > Hi again Scott
> >
> > Responding to a couple of other emails, if you are really going to 
> > restore
> > your data only (as opposed to a mixed release migration) then it doesn't
> > make a lot of sense to bother with the V5R3 step. This does however make 
> > a
> > lot of sense if you are doing a mixed release migration as many system
> > settings will get preserved.
> >
> > If restoring only you would need to consider at least rebuilding the 
> > hosts
> > table, routing config, host & DNS configuration, system directory 
> > entries,
> > and relational database directory.
> >
> > I've found restoring QUSRSYS and QGPL using OPTION(*NEW) and excluding Q*
> > objects to work well in this kind of exercise as well.
>
> --
> 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.