[Info-vax] HP Integrity rx2800 i4 (2.53GHz/32.0MB) :: PAKs won't load

[Paul Sture]

On 2016-02-15, VAXman-  @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
> Hi,
>
> I'm working with a customer who has 2 HP Integrity rx2800 i4 (2.53GHz/32.0MB)
> (from $ SHOW CPU output).  Each has a separate system disk because they will 
> be clustered at disparate sites.  The PAKs on one of the nodes load but they
> do not load on the other.  I've checked that each node has different/unique 
> PAKs by authorization numbers.  Listed below:
>

...

> On NODE_2, a $ LICENSE LOAD returns:
>
> %LICENSE-W-NOLOAD, license was not loaded for OPENVMS-I64-BOE
> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
> %LICENSE-W-NOLOAD, license was not loaded for VMSCLUSTER
> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
> %LICENSE-W-NOLOAD, license was not loaded for VOLSHAD
> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
>
> WTF?

$ LICENSE MODIFY /INCLUDE=(node-name[,node-name,...])

is your friend.

>From HELP LICENSE /MODIFY /INCLUDE

   Licenses for the OpenVMS operating system usually specify the
   NO_SHARE option on their PAKs. In a cluster environment you must
   restrict each of these OpenVMS licenses to a single node. If
   you did not do this when registering with VMSLICENSE.COM, enter
   LICENSE MODIFY/INCLUDE=node-name, specifying one SCS node name
   for each OpenVMS license.

-- 
There are two hard things in computer science: cache invalidation,
naming, and off-by-one errors.