|
Hello, all: I beg to differ with Al on this point... there IS a way to upgrade from ANY release of OS/400 to ANY newer release... even from V2R3 to V5R1, directly, in one step... it is called a "scratch load" (or "Load and Initialize" in IBM-speak)... This is just like formatting the hard drive and then re-installing the MS Windows OS, which usually works much better than trying to "upgrade" from one version of Windows to another... :-) Here is how it works... first you carefully make back-up tapes of your entire system, on the old release, especially, you want to study the IBM Backup & Recovery Guide with regard to saving all of your configuration objects (SAVCFG) and security data (SAVSECDTA), and of course, save all of your user libraries, and QGPL, etc. If you use the IBM supplied "GO SAVE" menu, option 21, to save the "entire System" it will save all this stuff, but it will also save the OS/400 kernel, which is a good idea in case something goes "terribly wrong" during the upgrade, and you need to restore... Make sure you clean the tape drive heads, etc., prior to back-ups... And you might want to make two separate full back-ups, just to be "safe"... Then, you begin with the "I_BASE_01" CD, and put it in the CD drive, and set the IPL source to "D" and re-IPL from the CD --PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(D), to replace the SLIC. When the menu comes up, you want to select "Load and Initialize" (scratch-load). This will "wipe" whatever data is on the load-source DASD, and then you will be prompted to add other DASD to the configuration later. Installing the SLIC is (more or less) described in Chapter 3, Task 1: Replacing the Licensed Internal Code. But, note that in the V5R1 Software Installation manual, I could not find a good description of the "Load and Initialize" options. But, just carefully choose that menu option, and once you get past that step, the rest should be as described in the book. (I think the "Load and Initialize" stuff may be documented in the full "Backup and Recovery" manual.) Then, you follow the instructions in the OS/400 V5R1 "Software Installation" manual, Chapter 6 "Installing Software on a New iSeries Server (without the Operating System installed)." Anyway, I have found that this method works much better than the "Automatic" upgrade, or even the "Manual" upgrade procedures that IBM provides. This all works because, no matter what release you install, you can ALWAYS restore saved objects from tape from ANY PRIOR version/release, all the way back to System/38. :-) I hope this helps... Regards, Mark S. Waterbury ----- Original Message ----- From: "Al Barsa" <barsa@barsaconsulting.com> To: <midrange-l@midrange.com> Sent: Friday, August 16, 2002 7:34 AM Subject: Re: 5.1 upgrade > > Hi, > > You cannot go from V4R3 to V5R1 (without phenomenal pain). You must go > from V4R3 to V4R4 or V4R5 (which of course is no longer available from > IBM), and then go from wherever to V5R1. > > Might I suggest that you skip V5R1. Go from V4R3 to V4R5, and then from > V4R5 to V5R2. V5R2 is an exceptionally stable release, and V5R1 kinda > @#$%ed. As you have to do a two step move, do it that way. > > Al > > Al Barsa, Jr. > Barsa Consulting Group, LLC > > 400>390 > > 914-251-1234 > 914-251-9406 fax > > http://www.barsaconsulting.com > http://www.taatool.com > > > > > > > kmskeele@mail.volusi > a.k12.fl.us To: midrange-l@midrange.com > Sent by: cc: > midrange-l-admin@mid Subject: 5.1 upgrade > range.com > > > 08/15/2002 09:50 AM > Please respond to > midrange-l > > > > > > > I am new to this aspect of upgrading the iseries. Is there a site or > something that I could find any charges that would be incurred by upgrading > my OS lease from 4.3 to 5.1 ? No CA or anything > special. Currently using Mocha5250. TIA > > > > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > ********************************************************************** > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.