[Info-vax] VAXCluster vs. VMSCluster?

[John Santos]

In article <alpine.LFD.2.00.1001071014240.5236 at libra.gmcl.internal>, 
mylastname at gmcl.com says...> 
> On Thu, 7 Jan 2010 at 15:57 -0000, AdeV wrote:
> 
> > My hobbyist licences included "VMSCLUSTER". But, once I'd run 
> > CLUSTER_CONFIG.COM & got it to go through without error, on 
> > re-booting I get the following messages:
> >
> >  %%%%%%%%%%%  OPCOM   7-JAN-2010 15:23:28.42  %%%%%%%%%%%
> >  Message from user SYSTEM on ASTVAX
> >  %LICENSE-E-NOAUTH, DEC VAXCLUSTER 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
> >
> >
> >  %LICENSE-E-NOAUTH, DEC VAXCLUSTER 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
> >  Startup processing continuing...
> >
> > The licence is called VMSCLUSTER, not VAXCLUSTER - is that, 
> > technically speaking, a different product?
> 
> Dunno.
> 
> $ SHOW LICENSE
> 
> Does either VMSCLUSTER or VAXCLUSTER appear in the list?  If not, then
> 
> $ LICENSE LOAD VMSCLUSTER
> 
> No errors?  SHOW LICENSE again.  Is it there now?

I don't think any of the replies have made this clear...

If you want to have a cluster of two nodes (one a SIMH and one
a real MicroVAX), you need TWO base VMS licenses.  You can't
install one license and mark it to /include=(node1,node2).  It
is trivial to get multiple VMS base licenses from the hobbyist
site.  Just specify the hardware type as "SIMH" (or whatever kind
of VAX you are emulating), and specify a unique serial number
of your own choosing.  (You can use the serial number of the host
PC or just make one up.)

Then register your new license in the cluster LMF database and
/include one of your nodes.  Use /include to set the other VMS
license to enable the other node.  Use /AUTH=xxxx to distinguish
the licenses in the "$ license modify" commands.



VMSCLUSTER vs. VAXCLUSTER licenses...

Originally, the name of the license was VAXCLUSTER, but when the
Alpha port occurred, they changed the name to VMSCLUSTER.  The
cluster code checks for a valid, loaded license with either name,
so I think either should work, though I'm not certain of this.
The hobbyist LP license set includes both a VAXCLUSTER license
and a VMSCLUSTER license, and works on both VAX and Alpha.  I'm
not sure if the VAXCLUSTER license is ignore on Alphas and vice
versa, but it doesn't hurt to register and load both of them on
all your systems, regardless of architecture.


-- 
John Santos
Evans Griffiths & Hart, Inc.