Modules > Asset Management > Software License Management > Authorization Analyzer (Complex license types) > AA Functions > Func48

Description

This function is a specialty function that is designed to check the sum of license units required (LURs) for the MSL title associated with the authorization under test across a group of devices that are being used by the same user (person).

This function is primarily used to adjust LUR counts for license types that are assigned by device however allow the user to install and run the software on more than one device under the same license.

For example, if the license allows the right of second use (meaning the same user can run the software on up to two machines), this function will zero out the LURs of one authorization and leave the remaining authorization LUR count as 1, to indicate 1 license required to cover both deployments.

NOTE: This function uses the custodian login ID of the associated devices to determine the devices in use by the same user. Therefore, the MIE's custodian feature must be enabled.

NOTE: This function is intended for use primarily on workstation titles where the LUR value for any given authorization is either 1 or 0.

Processing Notes

This function goes through the following steps to derive the required answer:

•Checks to make sure the asset under test has a custodian defined and that the authorization under test has an asset record associated with it.

•Given the checks pass, all active authorization records for the MSL title under test are collected across the base of assets in use by the same custodian.

•The LURs are summed across the resulting authorization records.

•The summed LUR count is divided by the maximum devices allowed per user parameter that is specified, then raised to the nearest integer. For example, if a maximum of 5 devices per user is specified and the current LUR count for the current user is 6, the result would be 6/5 = 1.2, raised to the next integer = 2. The result is the number of licenses required to cover the current number of deployments.

•The resulting value from the previous step is then used to write a LUR count of 1 into the number of authorization records equaling the number of licenses required. For instance, if 2 licenses are required, then two authorization records will have their LUR counts set to 1. The authorizations are ordered by date created, least to most recent, when deciding which authorization records end up with their LUR counts set.

•All remaining authorization records (if any) will have their LUR counts set to 0.

Inputs

Parameter	Explanation
Maximum devices per user	A text value that will be interpreted as a number that will be used as the maximum number of devices on which the same user can install and run the MSL title under test on one license. Accepts tags as well as AA-specific tags. If this value is non-numeric (after tags have been evaluated) or otherwise evaluates to 0, 1 will be used.
Advanced reason code (Optional)	An advanced reason code can be assigned to authorizations that are altered by this function.

Outputs

Result	Result Explanation	Confidence Adjustment	Return Value
True	Required LURs was not equal to the sum of existing LURs across the devices in use by the current custodian. Authorization records were adjusted such that the sum of LURs across the collection of authorization records for the current user and current MSL title equals the required LURs. The adjustments were made by the function, therefore -1 is returned so that no change is made to the current authorization under test by the calling program.	N	-1 (no change to current LUR)
True	The LURs required equals the LURs summed across all of the devices in use by the same custodian, signalling that no change is required.	N	-1 (no change to existing LURs)
False	No custodian was defined for the current asset under test Note - it is important in this case to ensure the LUR returned gets saved to the authorization record in order to correct for the case where this authorization was previously in a group associated with a given custodian, had its LUR value zeroed, and has now fallen from membership in that group. Its LUR value must be restored.	N	1
Else	One of the pre-processing checks failed or a general processing error was encountered. Check the thread log for details	Y	0

Func48_AdjustLURtoUser

Func48_AdjustLURtoUser