Configuring Job and License Checkout Matching

This is a challenging task because the information relative to the license handles is often incomplete and incorrect. For example, FlexNet Publisher does not report the checkout time to the second, and does not reveal the PID of the process that has requested the checkout. The PID alone would enable a precise matching. Instead, we have to accept the best possible solution based on approximate input data.

The matching is automatically enabled for all licenses.

When the number of running jobs for a given license exceeds about 1,000, the matching becomes onerous on the vovserver, which can be detected by "Long Service" messages in the vovserver log. For this issue, it is recommended to disable the handle matching for selected licenses.

When RDS Resource Management is Enabled

Edit the SWD/resources.cfg AVS resource management configuration file in one of two ways to assert the NOMATCH flag.

The recommended way is to assert the NOMATCH flag attribute directly in the feature rule object within the RESOURCE_MAPS array attribute:

{ 
    LICENSE_MONITORS=[ { NAME=”lm_cool_project” } ] 
    RESOURCE_MAPS = [ 
        { TAGS=”Blue”, FEATURES=”great_feature”, NOMATCH} 
    ] 
} 

Alternatively, the NOMATCH flag can be configured for a license feature using the top-level FLAGS array attribute:

{ 
    LICENSE_MONITORS=[ { NAME=”lm_cool_project” } ] 
    FLAGS = [ 
        { TYPENAME=”License:great_feature”, NOMATCH }, 
    ] 
    RESOURCE_MAPS = [ 
        { TAGS=”Blue”, FEATURES=”great_feature”} 
    ] 
} 

When Classic Resource Management is Enabled

Edit the Tcl configuration file SWD/resources.tcl to disable matching for a feature:

vovresSetFlags License:great_feature –nomatch 

# A less preferred method is as follows: 
# vtk_resourcemap_set License:great_feature -nomatch    

# The great_feature license feature is created by a vtk_flexlm_monitor  
# or vtk_flexlm_montor_all directive. 

vtk_flexlm_monitor_all 

Configuration Parameters that Control Matching

The following server configuration parameters control, configure, and limit Accelerator’s job and license checkout matching algorithm.