*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

 
downarrowCan I define the order in which different version licenses are issued?
Applies to: ARM Developer Suite (ADS), RealView Developer Suite (RVDS) 2.0, RealView Developer Suite (RVDS) 2.1, RealView Developer Suite (RVDS) 2.2, RealView Development Suite (RVDS) 3.0, RealView Development Suite (RVDS) 3.1, RealView Development Suite (RVDS) 3.1 Professional, Tool Licensing (License Management)

If you are managing a floating license server that handles licenses for multiple versions of the ARM development tools, then you may wish to ensure that the licenses for your latest toolchain are not consumed by older tools when older licenses are available.  The way to achieve this is dependent upon the version of the license server software you are using.  The version of FLEXnet/FLEXlm used by the client tools is not important.

FLEXnet v10.8 or later

When you request a particular feature, for example, v3.0 of the ARM compiler, and that version is defined in any of the INCREMENT lines within your license file, then the server software will issue a license for that exact version of the feature.

However, if you request a version of a feature that is not defined in any of the INCREMENT lines within your license file, then by default the highest available version of that feature will be checked out first. For example, if you have a mixed RVDS v3.1 and v3.0 license, and request a v1.2 compiler license, by invoking the ADS v1.2 compiler, the v3.1 compiler license will be issued first.

You can override this behaviour for a particular INCREMENT line by adding a SORT=nnn value into the server license file. The nnn value can range from 001 to 999.  The lower the value, the higher the sorting priority.  The default SORT value of 100 is used when SORT is not defined.

For example:

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

As long as the SORT value for the 3.0 compiler is lower than that for the v3.1 compiler, the 3.0 compiler license will be offered by the license server first.

Further information on sorting priorities in license files can be found in Appendix B of Macrovision's FLEXnet Licensing End User Guide.

FLEXlm v9.2 or earlier

If you are using v9.2 or earlier of the FLEXlm license server software then there is no guaranteed order in which licenses for different tools versions will be issued.  You might find that using an options file helps to control license increment use order. For more information please see the FAQ: Can I reserve floating licenses for specific users? .



Related:






back to top

*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow