Title: | VAX and Alpha VMS |
Notice: | This is a new VMSnotes, please read note 2.1 |
Moderator: | VAXAXP::BERNARDO |
Created: | Wed Jan 22 1997 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 703 |
Total number of notes: | 3722 |
I have a quick question about upgrade OpenVMS. I have a customer that is currently at 6.1 on a 7000 (Alpha). They will be doing an in-cab upgrade to an 8400 and adding options that will require 6.2-1h3 of OpenVMS. My question is this, is it a good idea for them to get to 6.2-1h3 on their 7000 and then do the in-cab upgrade? Can you go directly from 6.1 to 6.2-1h3 or do you need to go from 6.1 to 6.2 then to 6.2-1h3. Any help greatly appreciated. -bill
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
127.1 | EEMELI::MOSER | Orienteers do it in the bush... | Mon Feb 03 1997 01:47 | 8 | |
they need to go to V6.2 with an 'upgrade', then to V6.2-1H3 with an 'update'. The other option would be to go to V6.2-1H3 with an 'installation'. Sure they can first do the OS upgrade & update, and when things are ready do the hw thingy. /cmos | |||||
127.2 | See 8.* | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon Feb 03 1997 09:21 | 20 |
...is currently at 6.1 on a 7000 (Alpha). They will be doing an in-cab upgrade to an 8400 and adding options that will require 6.2-1h3 of OpenVMS. :My question is this, is it a good idea for them to get to 6.2-1h3 on their :7000 and then do the in-cab upgrade? If they want to preserve their existing environment, they should use the existing DEC 7000 to get to OpenVMS Alpha V6.2-1H3 (or to V7.1). Then perform the processor upgrade to the AlphaServer 8400 series. Make sure the customer knows they can _not_ run V7.0 on this particular system -- either V6.2-1H3, or V7.1 or later. :Can you go directly from 6.1 to 6.2-1h3 :or do you need to go from 6.1 to 6.2 then to 6.2-1h3. Any help greatly :appreciated. See note 8.* (currently 8.13) for the various upgrade path (also known as the upgrade and update path, in deference to Charlie) sequences. |