topic Re: Changing license in Operating System - OpenVMS

Changing license

Rickard_A — Thu, 02 Jul 2009 11:00:07 GMT

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.

Re: Changing license

Rickard_A — Thu, 02 Jul 2009 11:44:36 GMT

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

Re: Changing license

Steven Schweda — Thu, 02 Jul 2009 11:46:13 GMT

> 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.

Re: Changing license

Steven Schweda — Thu, 02 Jul 2009 11:55:58 GMT

> 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?)

Re: Changing license

Hoff — Thu, 02 Jul 2009 12:12:05 GMT

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.

Re: Changing license

Rickard_A — Thu, 02 Jul 2009 12:30:58 GMT

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

Re: Changing license

Rickard_A — Thu, 02 Jul 2009 12:35:12 GMT

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

Re: Changing license

The Brit — Thu, 02 Jul 2009 13:29:03 GMT

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

Re: Changing license

Hoff — Thu, 02 Jul 2009 14:20:55 GMT

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.

Re: Changing license

Rickard_A — Fri, 03 Jul 2009 05:44:18 GMT

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?

Re: Changing license

Duncan Morris — Fri, 03 Jul 2009 07:48:41 GMT

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).

Re: Changing license

Rickard_A — Fri, 03 Jul 2009 08:54:40 GMT

Thanks for the reply. I Assumed that it was phase V.

Re: Changing license

John Gillings — Sun, 05 Jul 2009 21:22:24 GMT

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

Re: Changing license

John Gillings — Sun, 05 Jul 2009 22:15:10 GMT

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.

Re: Changing license

Rickard_A — Mon, 06 Jul 2009 11:26:06 GMT

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

Re: Changing license

Rickard_A — Mon, 06 Jul 2009 11:28:19 GMT

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