If memory serves, DECnet (any phase) is covered by the OPENVMS-X86-OE or OPENVMS-X86-HAOE
OpenVMS licence paks pre-installed as part of the ‘community’ vmdk, so you should be able
to install the phase IV VMSINSTAL’ables and stop phase V from starting up in
systartup_vms.com
Just a thought
Keith
From: John H. Reinhardt [mailto:johnhreinhardt@thereinhardts.org]
Sent: 21 March 2025 20:39
To: hecnet(a)lists.dfupdate.se
Subject: [HECnet] Re: DECnet-Plus and Decnet Phase IV interoperability
On 3/21/2025 3:08 PM, Paul Koning wrote:
On Mar 21, 2025, at 4:04 PM, John H. Reinhardt
<johnhreinhardt@thereinhardts.org><mailto:johnhreinhardt@thereinhardts.org>
wrote:
On 3/21/2025 12:47 PM, Paul Koning wrote:
On Mar 21, 2025, at 11:19 AM, Peter Allan
<petermallan@gmail.com><mailto:petermallan@gmail.com> wrote:
I have DECnet Phase V set up on my x86 community package running VMS 9.2-2, mainly because
it did not come with Phase IV. That pushed me into learning Phase V "stuff"
after 30 years of managing to avoid it.
Hm, it's been a while but I thought the installation procedure for networking gives
you a choice, phase IV or V.
The OpenVMS install does, but the VSI Community License Program only give you access to a
pre-built VM which only has DECnet phase V installed.
I think I was using an earlier community release which wasn't quite so pre-built.
paul
Yes. It was about last April (2024) when VSI changed the format of the CLP from providing
PAKs and FTP access to install media to a pre-built VM with a version of x86 OpenVMS
installed with various LP and options and no access to install media.
--
John H. Reinhardt