[Info-vax] openvms licensing

[johnwallace4 at yahoo.co.uk]

On Thursday, 18 February 2016 20:13:06 UTC, Bill Cunningham  wrote:
> "Steven Schweda" <sms.antinode at gmail.com> wrote in message 
> news:93903b86-df3a-44ce-809d-20f0d692b477 at googlegroups.com...
> >> [...]  I have several DV* PAKs and UCX PAKs too. I might
> >> have to load them all. There is a VAX-VMS PAK.  [...]
> >
> >   The DVNET* PAKs are for DECnet.  As I wrote:
> >
> >>    If this is your only VMS system, then DECnet probably
> >> won't help much, so I'd start with VAX-VMS and UCX.  [...]
> >
> >   I would not bet my life on it, but I'd guess that the
> > plain UCX PAK would be all you'd need initially for IP
> > networking.  As I wrote:
> >
> >> [...]  If you need
> >> other PAKs, then you should get complaints about licenses
> >> when you restart the system.
> >
> >   But if you want to make more work for yourself, then who
> > am I to argue?
> 
>     I have a fully functional VMS now to keep. But I'm going to create 
> another VMS for trying to load a couple of liceneses into vmslicense.com 
> This command file asks for "product". There is no "product" on my license 
> file. I now see that is where "license register" is in the DCL command 
> language. So when running @sys$update:vmslicense.com, I know what goes in 
> product now. And it's not DEC.
> 
> Bill

Use your eyes, and the various examples which have been provided.

PRODUCT and PRODUCER are different parts of the PAK data.

PRODUCT should tell you what product the PAK is for.

PRODUCER should tell you the name of the vendor of the product.

DEC might be a sensible plausible value for PRODUCER name.

It probably isn't a sensible plausible value for PRODUCT name.

If you don't pay sufficient attention and you mux the two ip, it
don't work.