topic Re: License problems in Operating System - OpenVMS

License problems

Wim Van den Wyngaert — Wed, 27 Dec 2006 09:12:56 GMT

I have a AS 1000 with license openvms-alpha-adl of 3000, thus 30 users.

The openvms-alpha is 15 units of which 12 are taken.

I have 2 logins via decnet and thus show lic/us says 100 units used (1 connection is free).

But in console output I find "dec openvms-alpha use is not authorized on this node", "attempted use exceeds active license limits". This for each logon on the system (via rlogin or set host).

Why ???

Wim

Re: License problems

Jan van den Ende — Wed, 27 Dec 2006 10:13:34 GMT

Wim,

at the risk of "asking a stupid question":
Does the LDB show the correct nodename for the license?

Proost.

Have one on me.

jpe

Re: License problems

Volker Halle — Wed, 27 Dec 2006 10:20:44 GMT

Wim,

according to the Alpha License Ratintg tables, an AlphaServer 1000 should be using 15 units for it's operating system base license:

http://licensing.hp.com/swl/view.slm?page=alpha

What does $ SHOW LIC/CHARGE report for the Type A license ?

Volker.

Re: License problems

Wim Van den Wyngaert — Wed, 27 Dec 2006 10:25:04 GMT

Volker,

Mixup of systems. It's a AS500. 12 units required.

Jan,

To my knowledge, the include is not needed because this is not a cluster. And the license is loaded and used (with success because I can login, but I would expect no message in opcom).

Wim

Re: License problems

Volker Halle — Wed, 27 Dec 2006 10:50:26 GMT

Wim,

is the LMF$DISPLAY_OPCOM_MESSAGE logical defined ?

Volker.

Re: License problems

Wim Van den Wyngaert — Wed, 27 Dec 2006 10:52:32 GMT

Volker : yes (value TRUE).

Wim

Re: License problems

Volker Halle — Wed, 27 Dec 2006 10:53:32 GMT

Wim,

an OPENVMS-ALPHA license has the NOSHARE key option, so it requires the SCS nodename of the node it should be activated on. Try it...

Volker.

Re: License problems

Volker Halle — Wed, 27 Dec 2006 10:57:22 GMT

Wim,

when trying to check, whether a certain operation is covered by an active license, OpenVMS may check multiple different licenses. If the LMF$DISPLAY_OPCOM_MESSAGE logical is defined, each failing license check will send an OPCOM message. This logical should normally NOT be defined. Use it only for troubleshooting license problems, not for creating them ;-)

Volker.

Re: License problems

Wim Van den Wyngaert — Wed, 27 Dec 2006 11:03:08 GMT

Volker,

Tried with /include and no change after license load(as help says in /include : only for clusters).

If I understand correctly, the logical is badly set and it tries to find something that it doesn't find. But what is it searching for ? Isn't it essential in debug info to mention that ?

Wim

Re: License problems

Wim Van den Wyngaert — Wed, 27 Dec 2006 11:11:13 GMT

Found this :

14 Logical Name LMF$DISPLAY_OPCOM_MESSAGE

A previous version of this manual incorrectly stated that you
must define the logical name LMF$DISPLAY_OPCOM_
MESSAGE in order for messages to appear.

If you have already defined this logical name, you should delete the definition.

Define the LMF$DISPLAY_OPCOM_MESSAGE logical
name only if you are explicitly directed by Digital to do so (for debugging purposes). When defined, this logical name causes
many ``noise'' messages to be displayed on the operator's con-
sole; some of these messages can be confusing and misleading
to the point of suggesting that a product is not licensed when
in fact it is.

Wim

Re: License problems

Volker Halle — Wed, 27 Dec 2006 11:15:47 GMT

Wim,

OpenVMS interactive users could be licensed using different types of licenses. SYS$LOOKUP_LICENSE needs to check, whether any loaded license allows the interactive login attempt. It seems to check OPENVMS-ALPHA first, then OPENVMS-ALPHA-ADL. If the LMF$DISPLAY_OPCOM_MESSAGE is defined, each failed license check is logged, even if it is just one in a series of checks for various different possible license names.

Volker.

Re: License problems

Wim Van den Wyngaert — Wed, 27 Dec 2006 11:34:59 GMT

Modified the logical : solved.

Thx Volker.

Wim