RE: Going from v4r4 to v5r3 or 4 -- MIDRANGE-L

Obviously I did.  He's going to have to find a piece of trailer trash to
run on in the meantime.  A model 170 (they are just about free today) will
go to V5R3.  If I recollect correctly, there were some 170's that required
V4R5.  I looked at my last 170 presentation from '99, and there was no
mention.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

"i" comes before "p", "x" and "z"
e gads

Our system's had more names than Elizabeth Taylor!

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com



                                                                           
             "Wilt, Charles"                                               
             <CWilt@xxxxxxxxxx                                             
             om>                                                        To 
             Sent by:                  "Midrange Systems Technical         
             midrange-l-bounce         Discussion"                         
             s@xxxxxxxxxxxx            <midrange-l@xxxxxxxxxxxx>           
                                                                        cc 
                                                                           
             03/23/2006 12:43                                      Subject 
             PM                        RE: Going from v4r4 to v5r3 or 4    
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




Al,

I think you may have missed the post where the OP mentioned he is on a
150 and can't go above v4r4.

Gary,

I'd think this might be a time to consider hiring a BP to handle this
process.  Standard upgrades or same level RISC-RISC migrations are no
that big of a deal, but this....I wouldn't want to do it on my own as
there is no IBM supported method for doing it.

Good luck,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121


> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Barsa
> Sent: Thursday, March 23, 2006 12:27 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Going from v4r4 to v5r3 or 4
>
> You have two options.
>
> 1.    Do a scratch install.  Not my preference.
> 2.    Go from V4R4 to V5R1.  If you are going to immediately
> go to the next
> release (and not do any meaningful operations, don't PTF,
> except for the
> required PTF's for V5R3.  Then immediately go to V5R3.  Once
> again if you
> are not going to do any meaningful operations, then go to
> V5R4 and PTF.
> Note that both V5R3 and V5R4 have required PTFs from prior releases.
> Missing these is very painful.  Doing all of these convoluted
> steps means
> that you will preserve all your stuff, including data in
> QUSRSYS, system
> values, network attributes.  The last time we scratched (V5R1) was too
> painful to re-visit.
>
> Not to preannounce anything I might say at Soundoff, V5R4 is the third
> release in a row from IBM that is very stable out of the shoot.
>
> Al
>
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> "i" comes before "p", "x" and "z"
> e gads
>
> Our system's had more names than Elizabeth Taylor!
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
> http://www.as400connection.com
>
>
>
>
>
>              "Gary Kuznitz"
>
>              <docfxit@theoffic
>
>              e.la>
>           To
>              Sent by:                  Midrange Systems
> Technical
>              midrange-l-bounce         Discussion
>
>              s@xxxxxxxxxxxx
> <midrange-l@xxxxxxxxxxxx>
>
>           cc
>
>
>              03/23/2006 12:15
>      Subject
>              PM                        Re: Going from v4r4 to
> v5r3 or 4
>
>
>
>
>              Please respond to
>
>              Midrange Systems
>
>                  Technical
>
>                 Discussion
>
>              <midrange-l@midra
>
>                  nge.com>
>
>
>
>
>
>
>
>
>
> Hi Rob,
>
> Thanks for the input.
>
> On 23 Mar 2006 at 8:16, rob@xxxxxxxxx (rob@xxxxxxxxx
> <midrange-l@xxxxxxxxxxxx>) commented about Re: Going from
> v4r4 to v5r3 or
> 4:
>
> > "Should" is a business case.  I figure these people hate
> going through
> > upgrades if they are still running V4R4.  Therefore
> whatever you start
> > them out on they will probably be stuck with for a long
> time.  Therefore
> > I'd start them out on V5R4.
>
> I will defiantly end up with v5r4 on the box.  The only
> question is how I
> get
> there and how many hours it takes to get there.  I was hoping someone
> that has made that jump would chime in.   I don't know what
> conversions
> (under the covers)  have taken place at each version upgrade
> and if all of
> the changes will still get applied with such a large jump.
> At the moment
> I'm thinking of following Jim Franz's suggestion and:
> "If you just want to load your profiles and libs, I would stay at 5.3
> (making
> the difference between the 2 boxes the fewest skipped releases
> possible),
> load your stuff,
> then upgrade to 5.4 and apply ptfs."
>
> Of course I will apply the latest CUM on 5.3 and do a backup before
> loading any profiles and libs.  The down side is I'll need to
> do a bunch of
>
> testing three times.  Once on 5.3 to see if it was successful and then
> after
> I install 5.4 then again when I'm ready to update to the live files.
>
> I'm hoping someone else that has made the jump will tell me
> there wasn't
> any significant conversions done under the covers from 5.3 to 5.4 so I
> might as well just bite the bullet and see what happens from
> 4.4 to 5.4.
> If I remember right there was some internal conversion done
> from 4.4 to
> 4.5 and then again going to 5.1.  Is anyone in the know that
> remembers?
>
> Thank you,
>
> Gary Kuznitz
>
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > "Gary Kuznitz" <docfxit@xxxxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 03/22/2006 06:06 PM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> >
> > To
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > cc
> >
> > Subject
> > Going from v4r4 to v5r3 or 4
> >
> >
> >
> >
> >
> >
> > I have a new 520 being shipped tomorrow with v5r3.  I have
> an old box
> > running v4r4.  Does anyone know if I should load v5r4 on
> the 520 before
> > trying to convert from v4r4?
> >
> > Does anyone know how to convert from v4r4 to v5r3 or 4?
> >
> > Thank you,
> >
> > Gary Kuznitz
> > --
> > 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.
>
>

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