Hi

In addition to Roberto's suggestion you have the option of using "Previous
release to current release support" which allows for the restore and the
upgrade to be done in more or less one operation instead of two; so one
longer outage instead of two long outages. The scenario that works best for
you will depend on what kind of outage windows you have.

One thing you will be faced with is object conversion. You or your vendor
need to run ANZOBJCVN on your current system and be certain that all your
objects are ready to run at V7R1. Here is the IBM a link to the reference:
http://www.redbooks.ibm.com/redpapers/pdfs/redp4293.pdf

One reason I like the previous release migration strategy is that typically
the target machine is better resourced to do the object conversion and run
the upgrade process.

There are also PTFs you will need to put on your current system if you are
not up to date. Don't skip this preparation step.

Whichever way you go (upgrade current machine, then do an unload/reload vs
previous release migration) the key will be do to the requirements analysis
and rehearse what your are doing. You literally can't do too much
preparation. Don't skimp on doing the analysis to ensure your object
conversion requirements are covered; if they are done the upgrade itself is
fairly straightforward.



On Fri, May 27, 2016 at 9:07 AM, Bill Howie <blhowie66@xxxxxxxxx> wrote:

Hello all,

Quick and easy question for the group. We currently are running V5R4 on
our iSeries/i/etc. We are looking at upgrading to V7R1. At the same time
we're looking at migrating our machine to an offsite location to be
managed/supported by a third party vendor, which in our case would mean the
vendor would be purchasing a machine themselves and migrating our
applications to it as opposed to physically taking ours to another
location. We're hearing some interesting things from them that I am
wondering about. We are debating whether to migrate offsite first, and
then upgrade to V7R1, or go to V7R1 first. Our vendor is telling us that
"we are having a hard time locating a machine that will support V5R4",
which would enable us to do the migration first and then the OS update. Am
I not right in thinking that it doesn't matter what box we have as far as
migrating between releases? I mean, I think we could if we wanted to just
put our current box in a truck and take it to the new location and then
upgrade that SAME box and achieve what we're talking about. There's no
such thing in the iSeries world as a box that doesn't support previous
releases, right? Please, tell me I'm not crazy. Thanks all!

Bill
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.