Cluster licenses (X86)

Having difficulties when installing the system? Your system runs slowly and requires some tweaking? You can get help here.
Post Reply

Topic author
mickenx
Contributor
Posts: 12
Joined: Wed Apr 12, 2023 3:00 pm
Reputation: 0
Status: Offline

Cluster licenses (X86)

Post by mickenx » Wed Apr 12, 2023 3:02 pm

Hello,

I noticed that I can't load licenses on my clustered node. None of them works including the basic os license. It is like that in the manual , is this something that will be fixed or is it as is?

EDIT It is the community license.

Thanks,

Michael
Last edited by mickenx on Wed Apr 12, 2023 4:00 pm, edited 1 time in total.


marty.stu
Site Admin
Valued Contributor
Posts: 96
Joined: Tue May 21, 2019 6:56 am
Reputation: 0
Status: Offline

Re: Cluster licenses (X86)

Post by marty.stu » Thu Apr 13, 2023 3:55 pm

Hi Michael,

Please provide more information about the licenses installed on your system. Clustering is available as part of the x86 community license under the HAOE license. Some more explanations on the licenses can be found here: viewtopic.php?f=37&t=8603&p=18111#p18111.

So please at least provide the SHOW LICENSE command listiing.

Thank you.
Run to the bedroom, In the suitcase on the left You'll find my favorite axe.


Topic author
mickenx
Contributor
Posts: 12
Joined: Wed Apr 12, 2023 3:00 pm
Reputation: 0
Status: Offline

Re: Cluster licenses (X86) solved!

Post by mickenx » Thu Apr 13, 2023 5:42 pm

marty.stu wrote:
Thu Apr 13, 2023 3:55 pm
Hi Michael,

Please provide more information about the licenses installed on your system. Clustering is available as part of the x86 community license under the HAOE license. Some more explanations on the licenses can be found here: viewtopic.php?f=37&t=8603&p=18111#p18111.

So please at least provide the SHOW LICENSE command listiing.

Thank you.
On main node.

Code: Select all

Active licenses on node X86:

------- Product ID --------    ---- Rating ----- -- Version --
Product            Producer    Units PCL   Activ Version Release    Termination
ABS-CLIENT-X86     VSI             6  1     0      0.0  (none)       1-APR-2024 
ABS-SERVER-X86     VSI             6  1     0      0.0  (none)       1-APR-2024 
ACMS               VSI             6  1     0      0.0  (none)       1-APR-2024 
ACMS-REM           VSI             6  1     0      0.0  (none)       1-APR-2024 
ACMS-RT            VSI             6  1     0      0.0  (none)       1-APR-2024 
AVAIL-MAN          VSI             6  1     0      0.0  (none)       1-APR-2024 
BASIC              VSI             6  0     1      0.0  (none)       1-APR-2024 
C                  VSI             6  0     1      0.0  (none)       1-APR-2024 
CARTRIDGE-SERVER-V VSI             6  1     0      0.0  (none)       1-APR-2024 
CMS                VSI             6  1     0      0.0  (none)       1-APR-2024 
COBOL              VSI             6  0     1      0.0  (none)       1-APR-2024 
CXX-V              VSI             6  0     1      0.0  (none)       1-APR-2024 
DFG                VSI             6  1     0      0.0  (none)       1-APR-2024 
DFS                VSI             6  1     0      0.0  (none)       1-APR-2024 
DQS                VSI             6  1     0      0.0  (none)       1-APR-2024 
DTM                VSI             6  1     0      0.0  (none)       1-APR-2024 
DTR                VSI             6  1     0      0.0  (none)       1-APR-2024 
DVNETEXT           VSI             6  1     0      0.0  (none)       1-APR-2024 
FMS                VSI             6  1     0      0.0  (none)       1-APR-2024 
FMS-RT             VSI             6  1     0      0.0  (none)       1-APR-2024 
FORMS              VSI             6  1     0      0.0  (none)       1-APR-2024 
FORMS-RT           VSI             6  1     0      0.0  (none)       1-APR-2024 
FORTRAN            VSI             6  0     1      0.0  (none)       1-APR-2024 
GKS                VSI             6  1     0      0.0  (none)       1-APR-2024 
GKS-RT             VSI             6  1     0      0.0  (none)       1-APR-2024 
LSE                VSI             6  1     0      0.0  (none)       1-APR-2024 
MMS                VSI             6  1     0      0.0  (none)       1-APR-2024 
OMNI               VSI             6  1     0      0.0  (none)       1-APR-2024 
OPENVMS-X86-BOE    VSI             6  1     0      0.0  (none)       1-APR-2024 
OPENVMS-X86-HAOE   VSI             6  1     0      0.0  (none)       1-APR-2024 
OSAP               VSI             6  1     0      0.0  (none)       1-APR-2024 
PASCAL             VSI             6  0     1      0.0  (none)       1-APR-2024 
PCA                VSI             6  1     0      0.0  (none)       1-APR-2024 
RMSJNL             VSI             6  1     0      0.0  (none)       1-APR-2024 
RTR-CL             VSI             6  1     0      0.0  (none)       1-APR-2024 
RTR-SVR            VSI             6  1     0      0.0  (none)       1-APR-2024 
SAVE-SET-MANAGER   VSI             6  1     0      0.0  (none)       1-APR-2024 
SW-RAID5           VSI             6  1     0      0.0  (none)       1-APR-2024 
TDMS               VSI             6  1     0      0.0  (none)       1-APR-2024 
TDMS-RT            VSI             6  1     0      0.0  (none)       1-APR-2024 
VAXSET             VSI             6  1     0      0.0  (none)       1-APR-2024 
VMSCLUSTER         VSI             6  1     0      0.0  (none)       1-APR-2024 
VMSCLUSTER-CLIENT  VSI             6  1     0      0.0  (none)       1-APR-2024 
VOLSHAD            VSI             6  1     0      0.0  (none)       1-APR-2024 
X25                VSI             6  1     0      0.0  (none)       1-APR-2024
On the node that gives me the error ( when booted as part of cluster) ...- no licenses.
If I do LICENSE LOAD , I get errors for each license ,

example:
%LICENSE-W-NOLOAD, license was not loaded for OPENVMS-X86-BOE
-LICENSE-F-EXCEEDED, attempted usage exceeds active license limits

In the installation manual , you can see license errors in the end, very similar to this.

This can ofc be a user error. I haven't dealt with clusters recently ( only vax). I remember entering licenses for all nodes. Maybe that is a issue?

Yes probably , need to sync the databases

**************

SOLVED

I had too many cores allocated (6) so when node started all was used :D

Thanks for your attention
Michael
Last edited by mickenx on Thu Apr 13, 2023 8:01 pm, edited 4 times in total.


sms
Master
Posts: 336
Joined: Fri Aug 21, 2020 5:18 pm
Reputation: 0
Status: Offline

Re: Cluster licenses (X86)

Post by sms » Fri Apr 14, 2023 12:10 am

Code: Select all

>  I had too many cores allocated (6) so when node started all was used :D

   That was about to be my guess.  So far, my x86_64 (virtual) systems
currently have only two cores.  One is still still running E9.2, but I
loaded the new Community PAKs on it, and it clustered up as expected
with my main IA64 system:

View of Cluster from system ID 1164  node: ITS             13-APR-2023 22:57:55
+-----------------------+---------+
|        SYSTEMS        | MEMBERS |
+--------+--------------+---------+
|  NODE  |   SOFTWARE   |  STATUS |
+--------+--------------+---------+
| ITS    | VMS V8.4-2L3 | MEMBER  |
| V87    | VMS E9.2     | MEMBER  |
+--------+--------------+---------+

   Note that the IA64 Community PAK set includes explicit VMSCLUSTER and
VMSCLUSTER-CLIENT, and Units = 0, not 6, as everything in the new X86
set has.  (Seeing all those 6's in the new stuff was why I was about to
make that guess.  Too late.)

Post Reply