Occasionally a license may not be checked back into the pool of available licenses. This document details the steps necessary to release the license that has stopped responding using the 'lmremove' command.
Before you can remove the license server and license files, you must terminate the license server using the FLEXnet Licensing tool lmdown (see “lmdown,” Section 3.6.2). Create a backup of any files you wish to keep, such as your Abaqus license file (typically named abaquslm.lic ) and the FLEXnet Licensing server debug log file (typically. To fetch the example input file c2.inp from the archive files, use the following command: abaqus fetch job=c2.inp To fetch all files associated with job c8 from the archive files, use the command abaqus fetch job=c8 In this case ABAQUS will extract both the input file (c8.inp) and the user subroutine file (c8.f).
- Online Documentation. The full ABAQUS documentation (latest version) can be accessed on gra-vdi as shown in the following steps. In the address bar type about:config (hit enter) - click the Accept the risk button. In the search bar type uniqe then double click privacy.fileuniqueorigin to change true to false.
- There is an easy way to check how many tokens you have available and in use using the command prompt. On any machine that is connected to the server, open a command prompt. For FlexNet type in. Any folderabaqus licensing -ru. And hit enter For DSLS. Any folderabaqus licensing dslsstat.
- Jan-2019: Part1) The sharcnet Abaqus license has been renewed until 17-jan-2020. Users and/or the PIs are going to be required to sign an academic license agreement this year to confirm there will be no commercial use of the software. Previous users will be emailed soon to request signing the agreement.
When a license is checked out, and either the license server or the machine running the software stops responding, the license is not made available for use by others until it is released.
Solution or Workaround
The steps given below require that the reader be at or remotely logged into the License Manager server.
The example below uses the following information:
- Feature - ARC/INFO - This is the unreleased license.
- User - Username - The user name of the person who checked out the license.
- Host - SERVERNAME - The host name of the machine that the license was being used on.
- Port - 27004 - The port the License Manager uses to communicate.
- LM_Server - redoctober - The host name of the License Manager server.
- Handle - 104 - A unique identifier for the license session.
- Using the command line, go to the License Manager directory.
- Obtain the information for the required fields of the lmremove command by running the license manager status command.
Example of the output from the lmutil lmstat command:
- Check the output returned from the lmstat command to select the license that is to be released.
- The proper syntax for the lmremove command is:
- Using the '-h <feature> <host> <port@LM_SERVER> <handle>' option:
Using the 'lmutil lmremove <feature> <user> <host> <display>' option:
- It is possible that the display information is encrypted. Such is the case here:
In such cases, it is best to use the lmremove option '-h <feature> <host> <port@LM_Server> <handle>', unless the license manager is pre ArcInfo 7.2.1 or pre ArcView 3.1. When the display is encrypted, it may contain special characters, such as , (,), ~, which will not be read for their text value. Use the double quotes when encountering such characters. For example:
Last Published: 11/24/2020
Article ID: 000001400
Abaqus’ licensing structure is intended to be flexible enough to be appropriate for a single consultant or for a fortune 100 company. As always, with flexibility comes complexity. The purpose of this article is to unpack the options and help you choose the best configuration for where you are today. I say today, since usually it is not an issue to change to a different strategy at a later date.
The licensing is token-based just like what you find in an arcade where some games take 1 token and others may require more. I’ll break this down to tokens needed for Simulation and GUI with a middle section on the various types of tokens.
Token requirements for running a simulation follows a simple equation:
Where T is number of Tokens and N is the number of CPU cores or processing units for the run to solve on. With increasing numbers of cores the computation power increases dramatically, so your analysis will solve faster, but the gain is not quite linear. What’s more, this equation tells us that a solve with 1 CPU core takes 5 tokens while 2 cores will require 6 tokens. Adobe zii 2020 5.3. That’s only one more to roughly cut the solve time roughly in half! This progression is shown in the table below.
If you were reading closely and checked out the table things stop making sense at 12 cores since.
The actual equation is:
There are two possible reasons for this: first is the likely one and the second my made up one. Feel free to choose your favorite (I’m sure there is a deep rooted psychological reason for your choice):
Abaqus has provided a decaying token function to help balance the cost of significant parallel processing. If this wasn’t the case the 128 core job would require 132 tokens as opposed to the actual amount of 38.
Abaqus is full of people who would rather solve partial differential equations than play Sudoku and the licensing guy felt left out and created this formula.
There are a variety of license types. In this section I’ll go over the current ones. In the future Advanced Abaqus Licensing article I will go into more depth. Abaqus licenses are denoted by 3 letter ‘trigrams’. Three licensing types will be discussed in this section: Conventional, Extended and Portfolio. If you are a new user of Abaqus you can simply skip to the Portfolio section, since those are the tokens that will probably make the most sense for you.
Conventional (QAP, QAT, QAE)
QAT are analysis tokens
QAE are GUI tokens
QAP is a pack of 5 QAT tokens and 1 QAE token
The QAP pack is the minimum license build to allow authoring and running of Abaqus.
Extended (QXP, QXT, QAX)
In addition to Abaqus Extended tokens allow you to run the Extended Products (Isight, Tosca and FeSafe)
QXT are analysis tokens
QAX are GUI tokens
QXP is a pack of 10 QXT tokens and 1 QAX token
Portfolio (QPP, QPT)
Portfolio tokens are flexible because they can act as analysis licenses or GUI licenses. For analysis they behave the same as the other analysis tokens (QAT, QXT). For GUI application 4 tokens equal 1 GUI token (QAE, QAX)
QPT are analysis or GUI tokens
QPP is a pack of 5 QPT tokens and is the minimum license build to allow authoring and running of Abaqus. However, the GUI must be closed to release the 4 tokens to allow for the simulation to run.
After all that this section will be easy. Depending on your license type to run the GUI Abaqus/CAE you simply need either:
Conventional: 1 QAE
Extended: 1 QAX
Portfolio: 4 QPT
Abaqus License Check Command Center
As mentioned above, in general for new Abaqus users the Portfolio tokens are the best starting point. A portfolio pack of 5 tokens lets you run the Abaqus/CAE GUI for preprocessing and postprocessing and it gives you enough tokens to run the solver with 1 CPU core. From there, additional tokens may be added to reduce solve times or enable the GUI to remain open while a solve is being executed.
Hopefully this has helped to give you a clear understanding of Abaqus’ licensing system. Please let me know if you have any questions or if you are interested in purchasing Abaqus.
Abaqus License Check Command
Abaqus License Status Command
*UPDATE – New ‘Abaqus 2016 Price Calculator’ posted in the blog article below*