Hi Mark,
It's actually really straightforward; I had a VMScluster set up and I was
worried that switching versions of DECnet in and out might break
something... but no trouble at all.
(1) Make sure you have the DECnet Phase IV kit on hand, either on CD-ROM or
locally on disk on the machine in question. If you are planning to get the
Phase IV kit from CD-ROM and you're using an external CD-ROM that isn't
normally connected to your machine, I'd suggest shutting the machine,
hooking up the CD-ROM and then bringing it back up prior to doing the
switch, just so that the Phase IV kit is handy.
(2) Log in as SYSTEM and just type -
PRODUCT REMOVE
(3) Select DECnet OSI or whatever it shows up in there as (I no longer
recall exactly). It should be pretty clear which option in the menu
presented to you by PRODUCT REMOVE corresponds to DECnet.
(4) Let it go to work and remove DECnet... shouldn't take long... a few
minutes on my 4000/VLC or 3100/76.
(5) Once PRODUCT REMOVE has completed, just go ahead and install DECnet
Phase IV:
PRODUCT INSTALL DECNET_PHASE_IV
/SOURCE=DKAXXX:[...DECNET_PHASE_IV_VAX073.KIT]
(6) Reboot the machine (@SYS$SYSTEM:SHUTDOWN)
(7) Once the machine comes back up, configure DECnet:
@SYS$MANAGER:NETCONFIG
(8) Edit
SYS$STARTUP:SYSTARTUP_VMS.COM and uncomment the line that looks
something like,
START /NETWORK DECNET
(9) Reboot once more just for good measure (@SYS$SYSTEM:SHUTDOWN) and you
should be up and running!
My reference for this was just some ancient scrap of DEC documentation;
basically I just wanted something to confirm that I could switch one out
for the other without too much trouble, and figured it out from there :)
http://odl.sysworks.biz/disk$axpdocmar981/opsys/vmsos71/ovms_71_vax_install…
Note if you're running TCP/IP on the machine as well, be sure that the
system starts DECnet before it tries to start TCP/IP because DECnet does
some crazy MAC-address-rewriting on the machine and I guess it can't do
that if TCP/IP is already up and running... it gets confused.
If you have multiple nodes, you'll have to add them to the "DECnet hosts
file" via NCP before you can "resolve" them by name:
RUN SYS$SYSTEM:NCP
NCP> DEFINE MYVAX AREA.NODE
NCP> SET MYVAX AREA.NODE
NCP> EXIT
If any further questions, just let me know; happy to help... Once I got rid
of DECnet Plus, it all fell into place, pretty much :) I've tested with
PHONE and SET HOST between my two machines and everything seems to be
working well.
Best,
Sean
On Tue, Jun 10, 2014 at 2:06 PM, Mark G Thomas <Mark at misty.com> wrote:
Hi Sean,
I'm in about the same position as you, and would be interested in a link
to,
or copy of, the directions.
Mark
On Mon, Jun 09, 2014 at 06:32:18PM -0400, Sean Caron wrote:
Never mind; found some straighforward directions.
Sorry for the noise.
Best,
Sean
On Mon, Jun 9, 2014 at 6:20 PM, Sean Caron <scaron at umich.edu> wrote:
> Hi all,
>
> I have two VAX machines here running VMS under the hobbyist program;
it's
> been a whlie since I messed with OpenVMS
seriously and in my haste to
get
> going, I foolishly installed DECnet Plus
rather than DECnet Phase IV.
>
> Now I have a two-node cluster, but the nodes don't seem to be aware of
> each other outside of "SHOW CLUSTER". I can't perform network
operations
> including PHONE, SET HOST, etc. It just
always tells me that "the
remote
> node is not currently reachable".
>
> Is there a quick way I can uninstall DECnet Plus and replace with
Phase IV
> without having to take all the time out to
reload both of these
machines
> from scratch? I know there's gotta be at
least a few folks on here
that are
> conversant in VMS :)
>
> Thanks,
>
> Sean
>
--
Mark G. Thomas (Mark at
Misty.com)