On 02/12/2025 00:38, Wayne S via cctalk wrote:
Decnet needed a license.
I think that probably the license manager is called as part of running any
licensed product before you can do anything.
If you want to verify that it’s a licensing issue run a version of VMS before
V5 and install Decnet. Licensing enforcement came out with version five so
anything before that is not enforced.
Sent from my iPhone
On Dec 1, 2025, at 16:18, Peter Ekstrom <[email protected]> wrote:
It doesn't specify the symbols, just states some or missing.
But I ran netconfig.com<http://netconfig.com> and specified the name and decnet
address and specified end-node.
When I run startnet I get the following (I ran this manually but got it from the
startnet.com<http://startnet.com> script):
NCP>set known circuit all
%NCP-W-OPEFAI, Operation failure
Circuit = SVA-0
%SYSTEM-F-NOLICENSE, operation requires software license
What license is needed for circuits?
- Peter
On Mon, Dec 1, 2025 at 7:08 PM Wayne S
<[email protected]<mailto:[email protected]>> wrote:
What symbols? Can you show some here?
Maybe you have the wrong install script?
Sent from my iPhone
Firstly V5 checked the kernel considerably so anything tied deeply to it
(like DECnet) would need a new version, the V4.x stuff wouldn't work at
all. Although with DECnet, as has been pointed out that shipped with VMS.
From V5.0 onwards you would need a PAK (licence PAK). You need one for
VMS too, but it at least lets you log in once or maybe twice, so that
you can enter the required licence PAK(s).
For DECnet you get (IIRC) nothing without a licence PAK. Same for
clustering and volume shadowing.
So you are probably missing just a licence PAK for DECnet.
Before V5 most things just ran, but both VMS and DECnet had licence
tapes that increased the number of users allowed (in the case of VMS) or
allowed DECnet functionality (in the case of DECnet).
So even with V4 you had to do something extra to get DECnet running.
Antonio
--
Antonio Carlini
[email protected]
