vovserver Licensing

Each Accelerator product has a running vovserver with an particular product identity. The license features checked out, or validated in a license file, for the different Accelerator products are as follows.

Product Nickname Altair Floating License Features Altair License File Notes Reprise Licensing Features
Accelerator NC NCSltosFeature

The number of NCSlotFeature license tokens consumed by an NC tasker is the lesser of the number of configured NC job slots and the number of logical CPUs on the host.

The number of slots is identified by the SLOT attribute on the NCSlotFeature feature. server_nc, plus tokens of slots_nc

The number of NC slots_nc license tokens consumed by an NC tasker is the lesser of the number of configured NC job slots and the number of logical CPUs on the host.

Accelerator Plus WX

WXSlotFeature

WXSltoFeature tokens consumed by an Accelerator Plus queue nstance = (number of WX taskers in the base queue) + (number of logical CPUs on the Linux host where the Accelerator Plus server is running.

The number of slots is identified by the SLOTS attribute on the WXSlotFeature feature.

server_wx plus tokens of slots_wx

slots_wx tokens consumed by an Accelerator Plus queue nstance = (number of WX taskers in the base queue) + (number of logical CPUs on the Linux host where the Accelerator Plus server is running

Allocator LA LAJobFeature is the allowed jobs count. JOB attribute on the LajobFeature set to the job count server_la plus tokens of jobs_la
FlowTracer FT FTSlotFeature,FTSeatMFeature, FTSeatLFeature, FTSeatLXFeature,FTSeatGXLFeature,FTSeatUFeature For FTSlotFeature, the slot count is the SLOT attribute server_ft plus tokens of slots_ft, seat_ft_l, seat_fp_l, seat_ft_xl, seat_ft_gxl, or seat_ft_u
Hero HE HELeafFeature The SLOT and LEAF attributes are specified server_he
Monitor Basic LMS (none) server_lms (optional)
Monitor LM

LMUserFeature

One token per user.

The USER attribute is specified. server_lm One token of server_lm plus multiple tokens of user_licmon
To find out the product supported by a vovserver, use:
> source /<install_path>/<version>/<platform>/common/etc/vovrc.csh
% vovsh -x 'vtk_generic_get project info; puts $info(product)'
To change the value of RLM_LICENSE used by a vovserver, use:
> source /<install_path>/<version>/<platform>/common/etc/vovrc.csh
% vovsh -x 'vtk_server_setenv RLM_LICENSE 7070@newhost'

If vovserver loses a feature, it will keep running for a grace period of five days.

If the vovserver fails to get the appropriate license upon startup, or if the grace period expires, it will go into "License Violation", which essentially means that dispatching to remote taskers is disabled. Every other behavior remains fully functional.

To check the current licensing status, visit /cgi/license.cgi.