RE: AS400 software upgrade

["Lindstrom, Scott R." <Scott.Lindstrom@xxxxxxxxxxxxxx>]

No matter how much we begged and pleaded IBM would not sell us some V5R2 licenses.  So we cant run BRMS, for example.

Scott Lindstrom


-----Original Message-----
From: Pete Massiello - ML [mailto:pmassiello-ml@xxxxxxxxxxxx] 
Sent: Thursday, June 20, 2013 10:36 AM
To: Midrange Systems Technical Discussion
Cc: Lindstrom, Scott R.
Subject: RE: AS400 software upgrade

Really?

Before you get all excited, debate to go with this or go all the way to V5R4, how are you getting keys?  This is really important. Otherwise you have a 70 day timebomb.

	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 ldwopt@xxxxxxx
Sent: Thursday, June 20, 2013 11:33 AM
To: Midrange Systems Technical Discussion
Cc: Lindstrom, Scott R.
Subject: RE: AS400 software upgrade

Just to clarify

The upgrades were what we were told by the customer.

I am not sure why they want to stop at V5R2 but I was told that is the "newest release" that could be run on their hardware

We are in the process of laying out a process of what has to be done by both parties in order to accomplish this upgrade. 

I am saving all of the emails pertaining to this question in case the plan is accepted.

I appreciate all the fast comebacks. I am surprised some people have saved the media.

One last question, can this upgrade be completed without IBM software support contract?  We are exploring what software contracts the customer has on IBM and 3rd party software.  This may be a roadblock in the plan

Thanks
Dave
---- "Lindstrom wrote: 
> We jumped from V4R5 to V5R4 in one swoop but had a Business partner who knew how to do it. So greater than x-2 *can* be done.
>
> Scott Lindstrom
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
> Sent: Thursday, June 20, 2013 10:11 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: AS400 software upgrade
>
> Well, officially, you should respect the x-2.  So V4R1 should go to 
> V4R3 to V4R5 to V5R2.
> IBM has also documented an alternative path for such customers as this.
> Perform steps 25 through 33 in the topic "Restoring previous release 
> user data to a new system: Step-by-step instructions" in Chapter 14 of 
> the Backup and Recovery Guide.
> http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ipha8/books/sc
> 415304.pdf
>
> One thing to keep in mind is that V5 requires software keys.  That's 
> the first thing you had better check for!
>
>
> 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:   <ldwopt@xxxxxxx>
> To:     "Midrange Systems Technical Discussion'" 
> <midrange-l@xxxxxxxxxxxx>, 
> Date:   06/20/2013 10:17 AM
> Subject:        AS400 software upgrade
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Please try not to laugh at this request.
>
> Does anyone have the software for upgrading V4R1 to V4R4?
>
> We have a customer that wants to go to V5R2 but they are at V4R1.
>
> Step 1 is V4R1 to V4R4
>
> Step 2 is V4R4 to V5R1
>
> Step 3 is V5R1 to V5R2
>
> The system is a 9406-640.
>
> Thanks
> Dave Willenborg
> FNTS
> Omaha NE
> --
> 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.