Patick, >The latest copy (Jan 2001) of Midrange Computing announces that the V4R3 is >no longer for sale, and that it is required for upgrading to the later >releases (V4R5 & V5R1). It is required for an upgrade from an early RISC release like V3R7, but *not* for a CISC to RISC upgrade like V3R2 to VxRy. I just did a V3R2 to V4R5 side-by-side roadmap upgrade for a client last month. I also did a V3R7 to V4R3 to V4R5 last month, because V3R7 can't go to anything higher than V4R3 in a single step. >Are upgrades of this type better handled by starting from a clean box, and >restoring user libraries from the old system? You will undoubtably be starting with a new box, with the feature code 0203 to specify you are doing a "side-by-side" upgrade. This is one of the CISC to RISC roadmap options. It is much more detailed than simply restoring user libraries from the old system, but when followed to the letter is a straight-forward and reliable process. >Basically, how big a deal is this type of announcement -- long and >complicated, or just blowing smoke? It is a big deal for those on V3R6 and V3R7 -- early RISC release which did not require a software subscription. Doug +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.