using CC

[Levon Nikoghosyan]

Please help me to solve following problem
%LICENSE-F-NOAUTH, DEC C use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name

Please explain what I have to do and how I can receive the license

thanks in advance

[Ian Miller. · Accepted solution]

You need to load a licence for the C compiler.

(see LICENSE command)

You acquire the licences from HP or a HP reseller

[Steven Schweda]

> You acquire the licences from HP or a HP reseller

Or, for non-commercial use:

http://montagar.com/licenses.php

[Levon Nikoghosyan]

I have received license from montagar.com/licenses.php

but I don't know How I have to setup license using license command because the license is set to "license register VAX-VMS" - no any other choices provided on montagar.com

I am new on Vax system so may be some questions is very simple and stupid

Please help me completely setup CC


Thanks in advance

[Steven Schweda]

> I have received license from
> montagar.com/licenses.php

Which one(s)?

> [...] "license register VAX-VMS" [...]

Apparently the wrong one(s).

> [...] no any other choices provided on
> montagar.com

Really? Nothing there about "layered
products"? Are you sure? I'd look again.

Which sort of hardware (or emulator) are you
using? VAX, Alpha, or IA64?

[Levon Nikoghosyan]

>Really? Nothing there about "layered
>products"? Are you sure? I'd look again.

Sorry You are right :)


>Which sort of hardware (or emulator) are you
>using? VAX, Alpha, or IA64

my hardware is VAX 4000-400

Still I have a question - in the generated file I have found huge list of different licenses. Need I register all or I have to find out related to CC compiler ?

[Levon Nikoghosyan]

$ LICENSE REGISTER C - is this one is correct solution ?

[Hoff]

VMS software licensing is comparatively primitive and quite complex, and its implementation can sometimes unfortunately cause a system manager to become stuck in a complex and arcane environment when core PAKs are not available and not easily registered.

Some background...

There are two files of licenses that are necessary from the hobbyist program.

There is the base OS license set, and this set is architecture specific.

There is the layered product license set, and this is architecture-generic.

You need both sets; the base OS set and the product set.

The files containing the licenses that are generated from the hobbyist web site are usually DCL procedures that can be directly invoked via @(filename).

For cases such as this, this license product authorization key (PAK) registration gets tricky is when you don't have few core licenses loaded first. This is probably the most user-hostile part of LMF, as you basically have to break into the system from the console to get anywhere here.

Once you have a few core licenses registered and loaded, you can then transfer the rest of the files via the network or otherwise, and invoke the files containing the licenses to load all of the keys.

Here is some reading:

http://labs.hoffmanlabs.com/node/1692

and particularly:

http://labs.hoffmanlabs.com/node/259

[Steven Schweda]

> $ LICENSE REGISTER C - is this one is
> correct solution ?

That's the C compiler. As I recall, the
C compiler installation instructions mention
which PAK you need.

[Jan van den Ende]

Levon,

>>>
> $ LICENSE REGISTER C - is this one is
> correct solution ?

That's the C compiler. As I recall, the
C compiler installation instructions mention
which PAK you need.
<<<

Steven is correct.
But do not forget to LOAD the license.
The standard registration script DOES offer the option to LOAD (and does so by default, if I remember correct), but if not, then a license needs to by LOADed into memory by
$ LICENSE LOAD
before it can be used.

hth

Proost.

Have one on me.

jpe