Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Changing license

 
Rickard_A
Advisor

Changing license

I run VMS V5.1-1 and I cannot do the following:
$ncp set circ qna-0 state on

vms says that I dont got a license.
So I figured I could change the dvnetend license, because I have another.
But I dont know how.
lic del dvnetend doesnt work btw.
15 REPLIES 15
Rickard_A
Advisor

Re: Changing license

I added the new DVnetend and loaded it, but it didnt help. Any suggestions?
Steven Schweda
Honored Contributor

Re: Changing license

> I run VMS V5.1-1 [...]

Pretty old. You might try a couple of
commands to give us non-psychics some
information:

SHOW LICENSE DVNET*
LICENSE LIST /FULL DVNET*

> lic del dvnetend doesnt work btw.

As usual, showing actual commands with their
actual output can be more helpful than vague
descriptions and interpretations. "Doesn't
work" is generally useless as a problem
description.


General note on licensing: A PAK is not a
license, and a license is not a PAK.
Steven Schweda
Honored Contributor

Re: Changing license

> I added the new DVnetend and loaded it,

Can't see what you did.

> but it didnt help.

Can't see what happened.

> Any suggestions?

Provide more useful information?
(Consult a psychic?)
Hoff
Honored Contributor

Re: Changing license

If VAX/VMS is telling you that you don't have a license, then chances are, you don't. And if you think you have the necessary license, then you've either encountered a bug, or the license has not been accepted or loaded or is insufficient for the current platform or current license usage requirements, or your understanding of licensing or of the particular license required is incorrect.

If the DVNETEND license is correctly registered and loaded and you receive this error, then your Q-bus VAX/VMS V5.5-1 box is likely configured as a DECnet Phase IV level 1 or level 2 (area) router.

This host node status (and as end-node, router or area, IIRC) is displayed by:

NCP> SHOW EXECUTIVE CHARACTERISTIC

If your particular local host needs to operate as a router, then you'll need the DVNETRTG license.

Most DECnet LAN configurations will have one or more DECnet level 1 routers present, though it is possible to run DECnet on a LAN with no routers present.

It is fairly rare to SET a CIRCUIT STATE ON directly; that's usually part of the DECnet startup procedure STARTNET.COM, once DECnet has been configured via NETCONFIG.COM.

The DECnet Phase IV manuals are available on the OpenVMS Freeware V5.0 distribution:

http://digiater.nl/openvms/freeware/v50/decnet_phase_iv/

If I've guessed wrong here, please consider providing a few more details around the environment and the licensing and the DECnet configuration.
Rickard_A
Advisor

Re: Changing license

Sorry for being bad at explaining the problem. I cannot set circuit as seen below.
NCP> set circuit qna-0 state on
%NCP-W-OPEFAI, Operation failure

%system-f-nolicense, operation requires software license


Here is the information you asked for :)

$show license

active licenses on node:

DVNETEND
Producer: DEC
Units: 50
Version: 0.0
Date: (none)
Termination Date: (none)
Availability: E
Activity: 0
MOD_UNITS

Well thee are more licenses but not any DVNET.

$ license list /full dvnetend

License Management Facility

License Data Base File: TRASAN::SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1
Created on: 24-oct-1989
Created by user : system
LMF Version: V1.0
---------------------------
Issuer: DEC
Autorization: **************
Product name: DVNETEND
Producer: DEC
Units: 50
Version 0.0
Date: (none)
Termination Date: (none)
Availability: E
Activity: 0
Options: MOD_UNITS
Hardware ID:

Revision Level: 1
Status: active
Command: register

Rickard_A
Advisor

Re: Changing license

Thanks for the information Hoff.
I belive the Vax is set to be a router and I dont have the DVNETRTG license.
I will use the netconfig.com again and disable router.
Btw I have DECnet phase V
The Brit
Honored Contributor

Re: Changing license

2 comments.

1. I dont think DECNET Phase V was supported on OpenVMS versions before 7.0.

and

2. If you were running Phase V, then "NCP" is the wrong place to be. You should be in "NCL"

But Hey...

Dave
Hoff
Honored Contributor

Re: Changing license

DECnet Phase V (later known as DECnet/OSI and DECnet-Plus) was first available starting around 1991 or so.

Off-hand, I don't recall the supported version range for the earliest of (as it was then known) VAX/VMS and MicroVMS products.

And yes, the use of the NCP tool here does usually imply the use of DECnet Phase IV or (technically, and more likely here) of DECnet Phase IV+, and less likely the use of DECnet Phase V and its NCL management interface.

Rickard_A
Advisor

Re: Changing license

Maybe my problem is that Im running V5.1-1 and it cant handle decnet v5.0?
I dont have NCL.
And yes, Im sure I have decnet V5.0


NCP>show executor

Mode Volatile summary as of 3-JUL-2009 08:35:04

Executor node = 1.4 (TRASAN)

state = on
Identification = DECnet-VAX V5.0, VMS V5.1-1

The Vax harddrive crashed in 1998, so maybe the person that had the vax back then installed an old backup from 1988 that cant handle decnet V5.0?
Duncan Morris
Honored Contributor

Re: Changing license

You have V5.0 of DECnet Phase IV - the classic form of DECnet. This is the correct version for your version of VMS.

DECnet Phase V was a much later product (around VMS V5.5 timescale).



Rickard_A
Advisor

Re: Changing license

Thanks for the reply. I Assumed that it was phase V.
John Gillings
Honored Contributor

Re: Changing license

If this is a cluster, it could be misconfigured, so the PAK has been registered in the LDB, but not available to be loaded by this node.

Try $ SHOW LICENSE/USAGE/FULL from each node in the cluster.

If you want to find out exactly which product is being requested, do the following:

$ REPLY/ENABLE=LICENSE
$ DEFINE/SYSTEM/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE

Then repeat the failing command. You should see a sequence of OPCOM messages naming the products requested.

You should also check the LMF group table to see if you have any applicable group PAKs.

$ SEARCH SYS$UPDATE:VMSINSTAL_LMFGROUPS.COM

A crucible of informative mistakes
John Gillings
Honored Contributor

Re: Changing license

Sorry, forgot to mention...

Don't leave LMF$DISPLAY_OPCOM_MESSAGE defined. S
ome products can be authorized by multiple product names (for example DVNETEND and DVNETRTG). Those products will probe the LDB in some sequence. If a request fails, it will try another. LMF$DISPLAY_OPCOM_MESSAGE will cause a message to be issued for each unsuccessful probe, which means you may see false alarms. It should only be used for debugging.
A crucible of informative mistakes
Rickard_A
Advisor

Re: Changing license

It worked out. It was set to be routing without the right license for routing.
Rickard_A
Advisor

Re: Changing license

It worked out. It was set to be routing without the right license for routing.