| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
I have a customer who has a heavily customised V2.4 ALL-IN-1 cluster also running MR & MRX. They have decided that the work involved to sort all the customisation when upgrading to V3 is not warranted, so want to install a 'vanilla' ALL-IN-1 V3 system. Is it possible to 'overwrite' the V2.4 customisation, or do we have to do a virgin installation? If we have to do an installation from scratch, then there will be lots of work to install VMS and all associated layered products (ie MR, MRX, DECnet extensions, UCX, FMS, CDD, DTR, etc...), so any help that will allow us to 'upgrade' to ALL-IN-1 V3 will potentially save a lot of work. Any information before tomorrow would be appreciated because I have to discuss the options with them then, (as usual they want it done yesterday). Regards Alan
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3427.1 | Upgrade to V3.0 should be fine | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Thu Oct 21 1993 18:29 | 16 |
Hi, If they've done all their customisation using CM, and all their customised files are in the OA$SITE* directories, then they can simply move (or rename) all those files out of the way, upgrade to V3.0, and the V3.0 system will work "as normal". They can then re-instate their customised files (using CM, of course!), modified as necessary for V3.0, as and when they have time. If they've customised their system by changing modules directly in the OA$ base directories, then these will get overwritten anyay when they upgrade, so they have nothing to worry about! They should run the CART before upgrading, to see how "heavily" customised ALL-IN-1 thinks their system really is! Scott | |||||