4.2. Establishing User Licensing Preferences

Before running ANSYS, Inc. products, you should establish your licensing preferences, especially if you have multiple licenses at your site. Use the Set License Preferences for User option of the ANSLIC_ADMIN utility or choose Start > All Programs > ANSYS 18.2 > ANSYS Client Licensing > User License Preferences 18.2 to set your own licensing preferences. Note, preferences specified with this option apply only to you on the computer system on which the option was run and will not affect other users at your site.

You can use this option to review the licenses available, prioritize the licenses, and establish which licenses you will use. When you select this option, a dialog box opens. All licenses available to you on your license server machine(s) are shown under the appropriate tab:

You control the order in which the system attempts to check-out a license by moving the licenses up and down in the list using the Move Up or Move Down buttons. When you open an application, the license manager attempts to check-out the license listed first in the list. If unable to check-out that license, then the license manager attempts to check out the next license in the list that can be used by the application. The license manager will continue through the list until an available license is found. If none are found, a message displays.

By default, all licenses available from your license server are shown and marked as available for use. If you do not want a particular license to be available for your use, select the license in the list, and set the Use/Don't Use field to 0.

If you received a new license, you may need to reset your preferences. If you had previously set your license preferences using this option, add the new license to your list in the desired order.

If you have made changes to your license preferences, you can return the settings to the default state by selecting the Reset to Default button.

When you have completed your changes, click OK to make the changes and close the dialog box. Click Apply to make the changes without closing the dialog box. Selections you make here will take effect with any new sessions/license checkouts but will not affect the current session or change the license(s) currently in use.

If you are sending solve jobs to a remote compute cluster via Remote Solve Manager (RSM), note that your license preferences set for your local machine (the RSM Client) may not be the same as the license preferences set for the remote cluster machine (the Compute Server). In cases where local and remote license preferences are different, the preferences for the local RSM Client machine will not be applied when running on the remote Compute Server; instead, the preferences defined for the remote Compute Server will be used. If the license preferences and/or the licensing checkout order do not make the necessary licenses available to your remote solve, you must adjust the Compute Server preferences by setting your license preferences on the remote machine. Remote license preferences may be defined according to corporate IT policy, so see your license administrator about adjustments to Compute Server preferences.

4.2.1. ANSYS Workbench Licensing Methods

ANSYS Workbench users can also specify the licensing method to use.

ANSYS Workbench offers two licensing methods at Release 18.2:

  • Share a single license between applications (default) (shared mode)

  • Use a separate license for each application (separate mode)

Use the Licensing Preferences dialog box (Start > All Programs > ANSYS 18.2 > ANSYS Client Licensing > User License Preferences 18.2) to specify which method to use and which licenses to use. You must specify the licensing method before starting an ANSYS Workbench session. If you access the Licensing Preferences dialog box from the ANSYS Workbench Tools menu, you will not be able to choose a licensing preference from there.

Single License Sharing ANSYS Workbench allows you to work across multiple applications and workspaces in ANSYS Workbench while consuming only one of a single type of license per user per session. Using shared licensing, the active application holds the license, preventing other applications that are sharing that license from using it during that time. The application or operation requiring use of the license is called a concurrency event. For example, meshing and solving would each be a concurrency event.

Single license sharing allows you to progress through your analysis, from specifying engineering data through building or attaching a geometry, meshing, setup, solving, and finally, reviewing your results, all under the same license. The application holding the license must close or issue a PAUSE command, or receive an automatic release request to release the license and allow another application to use it. Licenses cannot be released while an application is actively performing a licensed operation (for example, an application cannot release a license in the middle of a solve operation; the license cannot be released until the solve operation is completed).

Single license sharing applies only to licenses of the same type (e.g., Mechanical). Choosing this option does not affect your ability to use licenses of different types simultaneously (e.g., Mechanical for one task and Fluid Dynamics for another).

Because this method is the default, you do not have to take any action to run this way.

Explanation of License Type and Examples License type is primarily by license feature. It is possible to use both a Mechanical and an Emag license within a single ANSYS Workbench session. It is also possible to use both a Multiphysics and a Mechanical license within a single ANSYS Workbench session.

The first license checked out within a session will be based on your preferences and what capabilities are being requested. For all applications other than the first (subsequent) one opened (within ANSYS Workbench), ANSYS licensing will first look at what other licenses are opened within this session. These subsequent license requests will look at sharing first to satisfy their request: do any other licenses being used within this session fulfill the needed capabilities? If yes, share an existing license. If not, preferences are used and a new, different license is checked out.

Example 1: You have one license for Multiphysics and one license for Mechanical, with Multiphysics listed first in your preferences. The first application starts and only needs capabilities in Mechanical. Since Multiphysics contains Mechanical capabilities and is first in your preferences, Multiphysics will be checked out. The second application starts and needs Multiphysics; since Multiphysics is already checked out, the second application will share it with the first. Only the Multiphysics license is consumed in this session.

Example 2: You have one license for Multiphysics and one license for Mechanical, with Mechanical listed first in your preferences. The first application starts and only needs capabilities provided in Mechanical, so Mechanical is checked out. The second application starts and needs capabilities provided on Multiphysics; since (the already in use) Mechanical cannot satisfy its requirements, it checks out Multiphysics. Both a Multiphysics and a Mechanical license are consumed in this session.

Restrictions of Single License Sharing You cannot run two concurrency events simultaneously (for example, you cannot mesh one model and solve another simultaneously) with one license.

If you are using a license for one application, other applications may still not be able to share that license if those applications require capabilities not supported by the license. For example, you cannot share a Mechanical license with a Fluent application.

Single License Sharing in ANSYS Workbench Applications ANSYS Workbench applications handle single license sharing differently:

The Mechanical Application:

You can launch the Mechanical application and move between its components (such as Meshing, Setup, and Solve). The active component will control the license while completing its operations and will release the license as soon as the operation is completed. For example, when you mesh, the Meshing component will control the license during the meshing operation and then immediately release the license when the operation is completed. The other components will remain in a read-only mode while Meshing uses the license, allowing you to view the data in other components but not operate on it.


Note:  Applications in read-only mode because of shared licensing do not refresh their license status automatically. Once the shared license is released by the editor that had consumed it, you must trigger Mechanical to query the license status. The most straightforward way to do this is click outside the Mechanical application window and then click back in the window to cause the license availability to be rechecked.


The Mechanical APDL Application:

This application consumes a license as soon as you launch it, and retains that license until it is finished. If you launch the Mechanical APDL application interactively, the license is retained until you either close the application or issue a PAUSE command at the Mechanical APDL command line. PAUSE allows you to temporarily release the license for another application to use. No other operation other than SAVE or /EXIT is permitted while PAUSED. When the second application has finished and releases the license, issue an UNPAUSE command from the Mechanical APDL command line to resume its use of the license.

CFX, Fluent, Autodyn, Polyflow:

These applications consume a license when launched and retain the license until they receive a request from another application to release it. For example, if you open CFX-Pre, CFX-Pre will obtain and control the license. It will retain the license until you close the application or until another application (such as the CFX solver) requests it.

Autodyn and Polyflow also provide a manual PAUSE feature that allows you to interrupt Autodyn or Polyflow and release the license, temporarily, for another application to use.

Separate Licenses  By using the separate-licenses method, ANSYS Workbench requires a separate license for each application. By using this method, you can move freely between the many applications that you might require during an analysis in ANSYS Workbench, provided that you have sufficient licenses. You can leave each application running and easily move between them at any point during the analysis, even if one of the applications is actively using the license (such as during a solve process). The disadvantage to this method is that you could potentially consume many licenses.

To activate the separate licenses method, choose Use a separate license for each application in the Licensing Preferences dialog box (Start > All Programs > ANSYS 18.2 > ANSYS Client Licensing > User License Preferences 18.2). You must specify the licensing method before starting an ANSYS Workbench session.

Examples of Using Separate Licenses You have two Mechanical licenses. When you open and mesh or solve a model in the Mechanical application, you consume one Mechanical license. If you link that Mechanical analysis to a Mechanical APDL system, you would consume a second Mechanical license when you launch the Mechanical APDL application, if you have not closed out of the Mechanical application. Neither of these licenses would then be available for other users until you closed out of one or both of the applications.

4.2.2. HPC Licensing

ANSYS, Inc. offers multiple high performance computing license options, described below. These license options apply to ANSYS, Inc. commercial and academic associate licenses only. These license options do not apply to ANSYS LS-DYNA; see the ANSYS LS-DYNA User's Guide for details on parallel processing options with ANSYS LS-DYNA.

The HPC license options below cannot be combined with each other in a single solution; for example, you cannot use both ANSYS HPC and ANSYS HPC Pack licenses in the same analysis solution.

See the applicable product documentation for instructions on configuring and running a distributed solution.

Notes on utilizing GPU acceleration:

ANSYS HPC

These physics-neutral licenses can be used to run multiple analysis jobs across multiple processors and work with most ANSYS, Inc. applications. The Mechanical APDL, Mechanical and Fluent applications can utilize any combination of CPU and GPU processors. Other applications are limited to CPU processors only. Contact your ANSYS sales representative for a complete list of applications that can be used with ANSYS HPC.

The Mechanical APDL application allows you to use two non-GPU processors without using any HPC licenses; ANSYS HPC licenses add to this base functionality. For example, a Mechanical APDL user using twelve processors (or cores) will consume only ten ANSYS HPC tasks.

The ANSYS CFD Enterprise, ANSYS CFD Enterprise Solver, ANSYS CFD Premium and ANSYS CFD Premium Solver applications allow you to use four non-GPU processors without using any HPC licenses; ANSYS HPC licenses add to this base functionality. For example, an ANSYS CFD Enterprise user using twelve processors (or cores) will consume only eight ANSYS HPC tasks.

ANSYS HPC licenses do work with ANSYS Workbench's Remote Solve capability; however, ANSYS HPC licenses are not subject to single license sharing as described in ANSYS Workbench Licensing Methods.

You cannot combine ANSYS HPC licenses with any other type of HPC licenses, including HPC Pack Licenses, in the same solution.

ANSYS HPC licenses are not valid with academic products; instead, use the appropriate ANSYS Academic HPC license.

ANSYS HPC Pack Licenses

These physics-neutral licenses can be used to run a single analysis across multiple processors and work with most ANSYS, Inc. applications. Contact your ANSYS sales representative for a complete list of applications that can be used with ANSYS HPC Pack Licenses. ANSYS HPC Pack Licenses enable parallel for single simulations according to the following schedule:

  • 1 ANSYS HPC Pack License per simulation: Combined CPUs and GPUs not to exceed 10

  • 2 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 32

  • 3 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 128

  • 4 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 512

  • 5 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 2048

  • 6 ANSYS HPC Pack License per simulation: Combined CPUs and GPUs not to exceed 8192

  • 7 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 32768

  • 8 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 131072

  • 9 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 524288

  • 10 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 2097152

  • 11 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 8388608

  • 12 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 33554432

  • 13 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 134217728

  • 14 ANSYS HPC Pack Licenses per simulation: Combined CPUs and GPUs not to exceed 536870912

You cannot use more than 14 HPC Pack Licenses on a single analysis. Individual HPC Pack Licenses cannot be split between multiple users or between multiple analyses.

Mechanical APDL allows you to use two processors without using any HPC licenses; ANSYS HPC Pack licenses function independently of this base capability. For example, a Mechanical APDL simulation using a single ANSYS HPC Pack License can access up to ten processors (or cores), as noted above, and not twelve processors (or cores).

HPC Pack Licenses do work with ANSYS Workbench's Remote Solve capability; however, HPC Pack Licenses are not subject to single license sharing as described in ANSYS Workbench Licensing Methods.

You cannot combine ANSYS HPC Pack Licenses with any other type of HPC licenses, including ANSYS HPC licenses, in the same solution.

ANSYS HPC Pack Licenses are not valid with academic products.

One ANSYS HPC Pack License can be borrowed at a time. Multiple HPC Pack Licenses or other HPC licenses cannot be borrowed.

Mechanical HPC, CFX Parallel Computing, CFD HPC, etc. Licenses

These physics-specific licenses will continue to work. The Mechanical APDL application allows you to use two processors without using any HPC licenses; Mechanical HPC licenses accommodate this feature. For example, a Mechanical APDL user with two Mechanical HPC tasks can access four processors/cores.

You cannot combine physics-specific HPC licenses with any other type of HPC licenses, including ANSYS HPC or HPC Pack Licenses, in the same solution.

4.2.2.1. Specifying HPC License Order

Use the HPC tab in the User License Preferences 18.2 dialog box to define the order in which HPC licenses are used. By default, the physics-neutral HPC licenses are listed before the physics-specific HPC licenses. If you want to change the order, select licenses and click the Move up or Move down button to reorder the list.

4.2.3. HPC Parametric Pack Licensing

ANSYS, Inc. offers additional license options called HPC Parametric Packs for ANSYS Workbench jobs requiring multiple design point updates. HPC Parametric Packs enable you to simultaneously update multiple design points of a single design study while using only a single license of each required base license. You must use the ANSYS Workbench reserved licensing feature to use HPC Parametric Pack licenses.

HPC Parametric Packs enable a specific number of simultaneous design points, as follows:

  • 1 HPC Parametric Pack: 4 simultaneous design points

  • 2 HPC Parametric Packs: 8 simultaneous design points

  • 3 HPC Parametric Packs: 16 simultaneous design points

  • 4 HPC Parametric Packs: 32 simultaneous design points

  • 5 HPC Parametric Packs: 64 simultaneous design points

You can use a maximum of five HPC Parametric Pack licenses per design study.

HPC Parametric Packs also work in conjunction with ANSYS HPC and ANSYS HPC Pack Licenses. Use the HPC licenses to enable multiple parallel processes to be used for each design point.

For more details on working with HPC Parametric Pack licenses in ANSYS Workbench, see Using HPC Parametric Pack Licenses in the Workbench User's Guide.

Additional Restrictions HPC Parametric Pack licenses have the following additional restrictions:

  • HPC Parametric Pack licenses apply to specific ANSYS, Inc. commercial licenses only; see your ANSYS, Inc. sales representative for a complete list of applicable licenses.

  • HPC Parametric Pack licenses are supported only on platforms supported by ANSYS Workbench.

  • HPC Parametric Pack licenses are not supported for Explicit Dynamics.

  • HPC Parametric Pack licenses are not available for borrowing.

  • HPC Parametric Pack licenses do not work with ANSYS Academic products.

  • HPC Parametric Pack licenses do not interact with Ansoft licenses hosted in ANSYS Workbench.


Release 18.2 - © ANSYS, Inc. All rights reserved.