7.3 Can I define the order in which licenses in a mixed version license file are issued?

Whether you can control the order in which licenses are issued by the server is dependent upon the version of the floating license server software you are using.

FlexNet v11.12.1.0 floating license server software

The FlexNet v11.12.1.0 floating license server software has a defined default order in which license files are sorted when parsed by the floating license server at startup. The default basic sorting rules within a single license file, from highest to lowest priority, are:

  1. INCREMENT entries are sorted alphabetically.

  2. Uncounted INCREMENT entries are issued before counted INCREMENT entries.

  3. Lower versions for an INCREMENT are issued before higher versions.


    The FlexNet documentation states that higher versions take precedence over lower versions but Flexera support has confirmed this is incorrect.
  4. Licenses with the most recent START= date, if specified, are issued before older licenses.

To define the use order of your licenses, add a SORT=nnn entry in the required INCREMENT line, where nnn is an integer from 000 to 255. The lower the SORT value, the higher the priority. The default sort value is 100. As this value is used when no SORT is defined by the user, lines with values less than 100 appear before unmodified lines, and lines with values greater than 100 appear after unmodified lines.

For example, if you have compiler INCREMENT entries in your license file with versions 3.1 and 4.0, you can ensure that the 3.1 license is made available first if you add a SORT attribute to the 3.1 INCREMENT as follows:

INCREMENT compiler armlmd 3.1 permanent 5 271940CDEFA0 \SORT=010 DUP_GROUP=UHD ISSUER="ARM Ltd" …

FLEXlm v9.2 or earlier floating license server software

If you are using FLEXlm v9.2 or earlier floating license server software, there is no fixed order in which licenses for different versions of tools are issued. This might mean that older versions of the development tools check out licenses for a newer version, even though the older licenses are available. You might find that an options file allows you to limit which users have access to what versions of a tools license. See 7.7 How can I limit user access to particular licensed features?.

Non-ConfidentialPDF file icon PDF versionARM DUI0577O
Copyright © 2011-2016 ARM Limited or its affiliates. All rights reserved.