[Info-vax] VAXCluster vs. VMSCluster?

AdeV spam at solutionengineers.com
Fri Jan 8 21:05:46 EST 2010


John Santos may or may not have intoned:
> 
> 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). 

Hi John,

Agreed, although I'd figured this out from other replies here + reading 
the various websites & FAQs that are out there. (NO_SHARE) means exactly 
what it says...

> 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.)

For my MicroVAX, I'd quite like to run a "pukka" version (with the 
actual serial number - not that I've figured out where that info is 
available yet); but I've not tried registering a second licence, is that 
possible with the same details? 

For now, it's cheerfully running with the Serial numberless licence.

> 
> 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.

Your words made me go and re-check the e-mail with my licences in, and 
sure enough I'd missed out "VAXCLUSTER" when I loaded them up 
(cut'n'pasted into a big file, get rid of all the continuation chars, 
save as a .com file; you get the rest). Somewhere along the line I lost 
the VAXCLUSTER line, but not the VMSCLUSTER one...

Now I've added VAXCLUSTER, the licence warnings have all gone away, and 
I can connect via t'internet again. Although, now I've got the MicroVAX 
running, I'll probably use that for the most part - there's something 
strangely theraputic about using an amber screen dumb terminal...


Many thanks, once again, for your assistance (goes for everyone).

-- 
Cheers!
Ade.



More information about the Info-vax mailing list