This article seems to suggest that when there are two activations for the same feature, then use of RESERVE for 2 licenses will result in the reservation of 4 licenses. In fact this is what we observe in our implementation using FlexNet 11.16.2 Example: .opt defined as: GROUP A Joe RESERVE 2 Feature_Name GROUP A Result is 2 licenses are reserved for Joe from each activation for the given Feature_Name for total of 4 licenses reserved for Group A (Joe). This article fails to discuss if this is by design nor is there any mention of an alternate workflow that might avoid doubling the number of reserved licenses. If however, we modify the feature name to include a keyword=value to identify a specific activation id only the desired 2 activations are reserved as desired. The following worked for our vendor implementation to avoid doubling the number of reserved licenses. GROUP A Joe RESERVE 2 Feature_Name:SIGN="1239 0FF9 68B0 59FB.." GROUP A Indeed this syntax results in only 2 licenses being reserved for group A (Joe). The problem then is that most client users only have the 42 character activation in hand and no specific information that might easily allow key word definitions as part of the feature. It's too bad that entitlement=[activation id] can't be used to single out the correct activation id .
... View more