V4R3 to V4R5

[David Abramowitz]

It was requested that I report back to the fora on this upgrade. We kicked all the users off the Model 620 at 6:00pm last night, and by 2:00am the release was completely installed. The only problem we had at all was with the licensed key information, but that was because the documentation was misplaced. Once found, we were fine. Dave

[J.Wells]

David, Thanks for the update. We will be going 4.3->4.5 on a 720 on 4.6.01 . Did this time include backup time? I will post our experience if there is any interest. Thanks, Joe

[Guest.Visitor]

Hey thanks for estimated time David. We haven't even gotten our CDs yet, so I haven't scheduled a date just yet. But did you use the Automatic update? Or did you go manual all of the way? But thanks for a rough guestimate. Nelson BTW, what do you have your performance adjustment set at? Do you do it or do you let the OS do it? Anyone else please feel free to chime in on that question also.

[David Abramowitz]

We used automatic update, but we did add new features. Performance adjustment is set to "1". Dave

[dbrunner@co.kenosha.wi.us]

Joe, I just brought 2 720s over from V4R4 to V4R5 on 3/4/01. My machines have > 1GB main on the chips, but of course the total time of the upgrade depends more on the number of programs you are upgrading. I spent 3.5 hours with the actual program upgrade. Then 40 minutes to load MF25209 prior to the 1005 cume. They don't tell you in the instructions, but you must first IPL to the "B" side before loading/applying this PTF. I had accomplished an earlier V4R4 to V4R5 upgrade on a 40S, and received a SRC A6005090 when attempting to load the required "pre" cume PTF, directly after the upgrade, while the machine was on the "A" side. After loading MF25209, and doing another IPL to apply, it only took 55 minutes for the C1005450 cume load. I did not auto-ipl with the cume, but rather followed up with DB Group SF99105. This load, plus the IPL took 25 minutes. Including misc, the entire process took 6 hours. Now just add your empirical backup time data to the front and rear of the process, and you should have a good idea what your total down time will be. Dale

[J.Wells]

Dale, Thanks for the tip. I have printed your response out and will add it to our reference stack for the 'big' night. Thanks, Joe