To ensure that you have sufficient licenses available for the duration of your design point study, you can reserve the licenses that are needed for design point updates.
To reserve licenses for a design point update:
Set up your design point study as you normally would.
Right-click the Parameter Set bar and select .
In the view:
Select License Checkout > .
Select Reserved License Set > .
In the Select Licenses dialog box, click each license under the Available Licenses tab that you want to reserve and click . You can select multiple licenses at one time by holding down the CTRL key as you click each license. The licenses you have selected appear in the Reserved Licenses panel. You can choose to filter the licenses shown by license type (Solver, PrepPost, Geometry, and so on).
When using an ANSYS HPC Parametric Pack license with either ANSYS HPC or ANSYS HPC Pack licenses, the number of licenses shown in the Concurrent Licenses column indicates the total number of HPC task available for the simultaneous design point update. For example, an HPC Parametric pack license used with eight HPC licenses shows 32 HPC tasks available because a single HPC Parametric Pack license enables four simultaneous design points, each of which can use up to eight HPC tasks. See Using HPC Parametric Pack Licenses.
You may be able to see what licenses were used for this study in previous updates by clicking the Used Licenses tab. See Tracking Licenses. You can add licenses to the reserve from this list as well.
To reserve more than one license of a given type, click the license in the Reserved Licenses panel and either click multiple times or type in the number of licenses in Change Number Selected at the bottom of the panel.
When you have selected all of the licenses you need to reserve, click . The selected licenses are not checked out at this time. License checkout occurs only when you begin the update.
If you are in an environment in which there may be contention for licences, you may want Workbench to check for reserved license availability as soon as possible, so that you know licences are available before you load data and attempt to update. To do this, clear Run-time Checkout of Reserved Licenses.
To instead check out reserved licenses at the start of the first job launched as part of a design point update, select Run-time Checkout of Reserved Licenses.
If the reserved license checkout fails for any reason, an error is reported in the RSM log.
Update your design points, either directly, or as a result of updating Design Exploration systems and components. The selected licenses are now checked out and held for the duration of the update.
If you have updated design points remotely via a queuing system for RSM, information on the reserved licenses is available to the job scripts in the ANSYS_RESERVED_LICENSE_INFO environment variable.
You can specify whether a pre-RSM foreground update uses reserved licenses. For more information, see Performing a Pre-RSM Geometry Update.
You see only those licenses that are available on license server machines that are in your license server path specification. You cannot see or reserve licenses from other license servers.
All machines used in your design point study must use the same license server.
If the license server that you are using is part of a triad and the triad's master server goes down, subsequent license checkouts behave as standard checkouts, rather than checking out licenses from the reserve pool.
You do not need to reserve licenses for DesignXplorer components because DesignXplorer does not check licenses out of the reserve pool.
If design points are being updated on remote resources using ANSYS Remote Solve Manager (RSM), the execution nodes must be accessing the same license server as the source project.
Do not use the ANSWAIT environment variable when reserving licenses.
Reserved licensing can be disabled by your corporate license administrator. You are warned when you try to use this feature if it has been disabled.
You might need to reserve a Geometry license even when the Geometry cell is not parameterized and is up-to-date, if either of the following situations is true:
If the project contains CAD geometry or any other geometry that is not managed by the Geometry cell but rather by a downstream Model or Mesh cell, and the geometry is parameterized via the Model or Mesh cell.
If an Engineering Data cell is parameterized and shares a model or mesh downstream with an unparameterized Geometry cell.
If you are using reserved Mechanical APDL licenses with RSM on Linux machines and you have the ANSYS182_PRODUCT environment variable set in a global login startup script that is used by all users on a machine, you may see update failures caused by license checkout errors. You should remove the ANSYS182_PRODUCT environment variable from any global login startup scripts. Note that if the ANSYS182_PRODUCT environment variable is set in a user's local startup script, or is set manually at runtime or via the launcher, the reserved licenses run correctly.
ANSYS Workbench tracks licenses that are used during an update. You can see what licenses were used for any cell by viewing that cell's properties. The property Last Update Used Licenses shows which licenses were used. You may find it useful to run the update of at least one design point as you normally would and then review the licenses that were used so that you know which licenses need to be reserved for a future study. License usage is tracked only for an Update operation in a component to which reserved licensing functionality is applied. It is not tracked if a cell becomes up-to-date as the result of an Edit operation.
Note: License usage is not tracked for DesignXplorer components. DesignXplorer uses reserved licenses indirectly by initiating design point updates.
License tracking may not return the information in some cases, such as if a cell was open for viewing or editing at the time of the update. In this case, Not Applicable is shown for Last Update Used Licenses, even though a license is used. To ensure that tracking captures information for all components, close all cells before updating.
Note: License tracking can be turned off by your corporate license administrator. If you run a study and do not see which licenses were used, see your license administrator.
If you are running a design point study and are using reserved licenses, you may need to free licenses if one or more design point runs hang or do not complete successfully. For example, you might delete a project that contains pending updates using reserved licenses. This situation should rarely occur. Typically, licenses are released if a design point fails. To free a reserved license, select . Select the projects for which you want to release licenses and click .
This utility removes any free or hung licenses in the reserve. If any of the reserved licenses are still in use, those running jobs continue to completion or until they attempt to check out further licenses. The design point study fails if it attempts to update further design points because the reserves have been removed.
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. HPC Parametric Pack licenses can be used for design point updates initiated from DesignXplorer. To use HPC Parametric Pack licenses, you must use the ANSYS Workbench reserved licensing feature.
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.
If you reserve more than one license of an individual licensed product, the HPC Parametric Pack license multiplies only one of the licenses (allowing four simultaneous design points when used with 1 HPC Parametric Pack). If you have multiple licenses specified in the Reserved Licenses panel when you add an HPC Parametric Pack license, the number of licenses is decremented to one.
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 example, if you specify that you want to run the ANSYS Mechanical solver for the design point
study using eight parallel processes for each design point, you must reserve the
necessary HPC licenses to enable eight parallel processes (one HPC Pack or six
processes of ANSYS HPC). The HPC Parametric Pack license allows all design
points to run using eight-way parallel processing. If
n design points are updated simultaneously, this
scenario uses nx8 cores, while consuming only one HPC
Pack or six processes of ANSYS HPC, as well as the license that enables the
Mechanical solver.
If a design point update involves more than one solver, the parallel licenses that you reserve
are available for use with both solvers running sequentially. For example, if
you define a design point study that uses both an ANSYS Mechanical and an ANSYS Fluent
license, and you specify that you want to use 8 parallel processes for Mechanical
and 32 processes for Fluent, you must reserve sufficient HPC licenses to
enable 32 parallel processes (2 HPC Packs or 32 processes of ANSYS HPC). The
HPC Parametric Pack license then allows all design points to run using up to
32–way parallel with both solvers involved in the design point study. If
you update n points simultaneously, this scenario
uses nx8 cores for ANSYS Mechanical and
nx32 cores for ANSYS Fluent, while consuming only 2
HPC Packs (or 32 ANSYS HPC processes).
If you have updated design points remotely via a queuing system for RSM, information on the reserved licenses is available to the job scripts in the ANSYS_RESERVED_LICENSE_INFO environment variable.
You can specify whether a pre-RSM foreground update uses reserved licenses. For more information, see Performing a Pre-RSM Geometry Update.
See HPC Parametric Pack Licensing in the Installation and Licensing Documentation for additional details about using HPC Parametric Packs.