|
midrange.com
2 years ago in January (with Al's gracious help in providing a bunch of
CD's) I had the joy of upgrading a Model 500 from V3R7 to V4R3 to V5R1. It
took just about 40 hours. I was able to read an entire Tom Clancy novel in
between prompts to load the next CD.
Paul Nelson
Arbor Solutions, Inc.
708-670-6978 Cell
pnelson@xxxxxxxxxx
Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/05/2004 12:26 PM
Please respond to Midrange Systems Technical Discussion
To: midrange-L@xxxxxxxxxxxx
cc:
Subject: Fw: Upgrade version V4R3 to V5R2
Resending a note from yesterday. This note absolutely did bounce.
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
----- Forwarded by Al Barsa/Barsa Consulting on 12/05/2004 01:25 PM -----
Al Barsa/Barsa
Consulting
To
12/04/2004 11:06 Midrange Systems Technical
AM Discussion
<midrange-l@xxxxxxxxxxxx>
cc
Subject
Re: Upgrade version V4R3 to V5R2
(Document link: Al Barsa)
You cannot do what your doing in one step.
What I would do is:
1.) Validate that you have no improperly coded trigger programs. These
will kill you (literally) on V5R1 or higher. To do this, run DSPFD
*ALL/*ALL TYPE(*TRG), and look for anything that isn't provided in OS/400
or LPPs using Query. If you attempt to do this to printout, it will make
one entry for every physical file on your system.
2.) Do a display of your installed software using the DSPSFWRSC command.
3.) Figure out what corresponding software you will need on V5R2. (IBM
keeps changing the names to insure that it never gets mindshare.)
4.) Assuming that you can get everything you need on V5R2 to be
comparable, they proceed.
5.) Double check that V5R2 will run on your hardware. the original
4xx/5xx hardware (shipped in 1995-7) will not support V5R2. (For that
matter, the new i5 hardware shipped this year will also not support V5R2.
I think that they actually pay someone at IBM to keep this complicated!
Steps to do this. A three day weekend is preferable, but not essential if
you can work hard and your system is fast enough.)
1.) Do a check for any required PTFs to go from V4R5 to V5R2, and get
these PTFs in advance. (Let's call them "V4R3 required PTFs".)
2.) Do a check for any required PTFs to go from V4R5 to V5R2, and get
these PTFs in advance. (Let's call them "V4R5 required PTFs".)
3.) Get 2 copies of V4R5. (You will likely have to get them illegally,
because IBM will no longer provide them. - The second copy is just
insurance.)
4.) Get 2 copies of V5R2. (I think that IBM will still give you one
legally. - The second copy is just insurance.) Be sure to get all of the
required "Group, Hyper and Cum. PTFs for V5R2.
5.) Make sure that you have a Support Line contract. If you need
support
for the "first upgrade" (I will define later.)
6.) Read all of the "Read this First" or "Memo to Users" (Whatever they
call it now.) for V4R4, V4R5, V5R1 and V5R2.)
7.) Install all of the "V4R3 required PTFs".
8.) Get two good backups of *EVERYTHING (GO SAVE option 21)
9.) Delete all LPP's and optional parts of OS/400. Do not delete QGPL
or
QUSRSYS, but all you want on your base system.
10.) Install only the base of V4R5, QGPL and QUSRSYS on top of your V4R3
System. (This is the "first upgrade" that I mentioned above. If you need
support, IBM may charge you for it.)
11.) Install all of the "V4R5 required PTFs" if there are any.
12.) Install of the V5R2 on top of V4R5. Be sure to install all of the
LPPs that you determined that you needed in step 3 of the first list
above.
There are many optional parts of 5722WDS, only install what you need. If
there are new optional parts of anything, also install them at this time.
(If you need support, your "support Line" contract should cover this.)
13.) Install all of the PTFs for V5R2 that you determined above that you
needed.
Do some sanity testing to make sure things work. Then get a good save.
Go home. I don't know how fast your hardware and memory are, but I did
the
almost equivalent of this for a customer last summer, and it took over 12
hours on a lowish end model 720. On 6xx hardware, I wouldn't recommend
anything less than a three day weekend unless it was a high end 640 or any
650 with gobs of memory.
Hope this helps.
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
"Suryawanshi,
Harish"
<Harish.Suryawans To
hi@xxxxxxxxx> "'midrange-l@xxxxxxxxxxxxx'"
Sent by: <midrange-l@xxxxxxxxxxxx>
midrange-l-bounce cc
s@xxxxxxxxxxxx
Subject
Upgrade version V4R3 to V5R2
11/30/2004 11:52
PM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Hi,
We are going to upgrade version of OS/400 from V4R3 to V5R2. What is the
technical issue. What impact on existing user application program. what
should be procedure and care ?
thanks in Advance
Harish
"DISCLAIMER: PLEASE NOTE "change in our mail id. It has changed from
@hpsglobal.com to @pstsi.com".The information in this message is
confidential and may be legally privileged. It is intended solely for the
addressee. Access to this message by anyone else is unauthorised.If you
are
not the intended recipient, any disclosure, copying, or distribution of
the
message, or any action or omission taken by you in reliance on it,is
prohibited and may be unlawful. Please immediately contact the sender if
you have received this message in error. Thank you."
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.
