Re: Upgrading from V5 to V7

And then, not always reading all the memos can help you. Take DS4700
storage for example, nowhere is it stated (except when it's broken already
and you're searching for a fix) that upgrading firmware from 6.xx has to go
thru 7.10.xx first, in fact it's not even avaiable in the ibm site for
download... The things i had to do to get that storage operational again
brr...
That's why i recommed not falling behind on updates be they firmware or
Operating System.
Of course when migrating an OS you can use a second system but still, the
headaches can be great.

Best Regards,

Roberto


On Fri, Mar 29, 2013 at 10:19 AM, Pete Massiello - ML <
pmassiello-ml@xxxxxxxxxxxx> wrote:

If you are upgrading from V5R3 to 7.1, sorry there is no supported upgrade
path. You can upgrade from V5R3 to V5R4 or V5R3 to 6.1, but that is it.
But I do agree with reading all the memo to users for the release
(singular) that you are skipping, and the one that you are going to.

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: Friday, March 29, 2013 7:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: Upgrading from V5 to V7

And why I encourage everyone to read the full Memo to Users for each
release they are either upgrading to, or skipping. For example, if you are
going from V5R3 to 7.1 then you should read the Memo to Users for V5R4, 6.1
and 7.1.

If you think something is too draconian in there and you must be
misinterpreting it; that IBM really wouldn't do that, then read it again.
Or ask this list - be specific.


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: Pete Massiello - ML <pmassiello-ml@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 03/29/2013 07:36 AM
Subject: RE: Upgrading from V5 to V7
Sent by: midrange-l-bounces@xxxxxxxxxxxx



One of the mis-conceptions with ANZOBJCVN.

When a program shows up on the Conversion Problem Report,
it means that it doesn't have either Observabiltiy or Creation Data. That
is really it. The assumption then that people incorrectly make is that
since a program is *NOT* on the list, then it will work. Not entirely
true. Having Creation data or Observability means that the program upon
crossing the 6.1 boundary will be able to be re-encapsulated, but it
doesn't guarantee that it will work.

This is why the best thing is to have a partition or test
environment where you can test out your programs on the new release before
your real upgrade.

This isn't to pick on Charles comments below, but just
want everyone to realize this, as I keep hearing this from people over and
over. "I Passed ANZOBJCVN so everything will be fine", not necessarily.

Happy Easter & Passover to all

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 Versfelt, Charles
Sent: Thursday, March 28, 2013 10:15 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Upgrading from V5 to V7

Pete Massiello asked:
subject: RE: Upgrading from V5 to V7
Do you have a program in that library that hasn't passed ANZOBJCVN ? is
this why you are asking?

My reply: Honestly I asked because my boss asked me to find out the
answer.
It was my application that used the library.

I assume from your question, if it doesn't show up in the ANZOBJCNV, we're
fine.
Our Operations Manager will be doing the ANZOBJCNV.

This email message has been delivered safely and archived online by
Mimecast. For more information please visit http://www.mimecast.com

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

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


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

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