Remove Licenses from a Preempted Job
% vovlmremove 00012345 00012355
The selection of utility calls lmremove, rlmremove, or vlmremove, is related to the licenses that currently match to the job.
Utility | Related License |
---|---|
lmremove | FlexNet Publisher license |
vlmremove | License emulation |
Automatic Call of vovlmremove for Suspended Jobs
The utility vovlmremove is automatically called by vovserver when a preempted job is in the SUSPENDED
state and matches some existing license handles. The utility attempts to free up the
handles that match. This functionality is called with a frequency controlled by the
parameter preemptionResourceRelease, which defaults to 90
seconds. This functionality can be disabled by setting this parameter to 0.
- A job has been preempted at least 60 seconds before and is currently in the
SUSPENDED
state (system controlled). - The job does not have the property
DONOTLMREMOVE
(user or system controlled).
vovlmremove
This utility removes all the license features associated with the given job.
vovlmremove: Usage Message
USAGE:
% vovlmremove [OPTIONS] <jobId> ...
This utility removes all the license features associated with the given job.
It uses 'lmremove' for FLEXlm licenses.
It uses 'rlmremove' for licenses that use a tag containing RLM.
It also works with Altair Engineering license emulation using 'vlmremove'.
Due to FLEXlm behavior, it is possible and expected for lmremove to fail if
it is called too early (typically 2 minutes after a checkout has occurred).
In such cases, vovlmremove should be retried after adequate time has passed.
OPTIONS:
-h Print this help message.
-v Increase verbosity
-prop Add a property called "PREEMPT_LMREMOVE" to the job to describe what
has been done.
EXAMPLES:
% vovlmremove 00012345
% vovlmremove 00012345 00022334
% vovlmremove -v 00012345
% vovlmremove -prop 00012345
% vovlmremove -h
Note
vovlmremove uses lmremove for FlexNet Publisher licenses. It uses rlmremove for licenses that use a tag containing RLM. It also works with Altair Engineering license emulation using vlmremove.
Because of the FlexNet Publisher behavior, it is possible and normal for lmremove to fail if it is called too early (typically before 2 minutes after a checkout). In such case, you can try to run vovlmremove again a bit later.