__Include: HASP License Content

 

The license data on a license key, independent of whether it is a hardware or software license key, consists of several parts: the license key text block contains the license section and one or more product sections. The license features describe additional conditions and limitations for the emulator products contained on the license.

A) License Key Text Block

1) License Section (one per license key)

The license section contains general license information related to ownership and administration.
There is one license section per license key. 
Please note that in rare cases, you may receive an empty USB dongle for which command outputs will show that no license information was detected. In such cases, request a license update from Stromasys as described in Updating a License.


Relevant license section parameters:

  • License type: type of the license, i.e., hardware or software license, network-enabled or local (added in newer Charon product versions, e.g., Charon-AXP/VAX 4.9)
  • License number: assigned by Stromasys
  • License key ID: unique; pre-programmed; unmodifiable; on physical keys same value as the Physical Key ID
  • Master key ID: the software vendor ID used by Stromasys for issuing licenses
  • Release date: the day on which the license was issued
  • Release time: the time at which the license was issued
  • Update number: the number of license updates that have been applied
  • End user name: the name of the person to whom the license was issued
  • Purchasing company name: usually the company to which the license was issued


2) Product Section (one or more per license key)

The text block also contains product sections that contain product specific licensing information.

  • Several products can be combined on one license key. Stromasys may place restrictions on what products can be combined on a single license key.
  • The product section also may include information about the support contract and the end of support. It may contain hardware specific limitations related to the types of devices that can be connected (e.g., serial interfaces).
  • A checksum is inserted after the last product section of a license. This checksum is not visible in the show command output. Charon products/versions requiring such a checksum will not start if the license does not contain a checksum.
  • Each product section is associated with a feature defining additional conditions for the product.


The following list shows the most important parameters of a product section.

Please note that not all of these parameters may be present for a particular Charon product.

  • Product License Number: identification of specific product section (optional; new starting with Charon-AXP/VAX 4.9 and Charon-PAR 1.10). Corresponds to configuration parameter license_id.
  • Virtual Hardware: range of virtual models available for running
  • Product Name: commercial product name
  • Product Code: commercial product code
  • Major Version, Minor Version, Maximum Build, Minimum Build: commercial product version and range of build numbers suitable for running with this license. The parameters Maximum and Minimum Build are no longer displayed starting with Charon-AXP/VAX 4.9 and Charon-PAR 1.10.
    Please note that, depending on the product and product version, licenses have a limited backward compatibility (i.e., when the version on the license is newer than the product version).
    See Operational Procedures Overview in the Sentinel HASP Licensing Documentation for more information.
  • Host CPU supported or 32bit and 64bit OS requirements: type of host CPU required (for example, x64)
  • Host Operating System required: Linux or Windows
  • CPUs allowed: number of virtual CPUs enabled for virtual multiprocessor systems
  • Maximum virtual memory: Maximum memory emulated. If not present the value defaults to the maximum memory possible for the particular virtual system. Note that the maximum memory may not be available to the virtual system if the host computer has insufficient physical memory.
  • CHAPI enabled: whether or not CHAPI (Charon-AXP API) can be used with this product
  • Instances allowed: maximum number of Charon emulator instances of this program/hardware model that are allowed to run concurrently on the local host. Relevant for local license keys that do not support the process count parameter. See also the parameter Number of processes in the feature section.
  • CPU Speed: optional parameter to reduce the speed at which the program can run to a fraction of the maximum (e.g., to 25%)
  • HPSUSAN: optional parameter. Specific to HP3000, overrides physical key ID. The HPSUSAN (HP System Unique Serially Assigned Number) is used for licensing purposes by HP. The parameter may be needed if a license on the physical system is tied to the original HPSUSAN.
  • Feature number: number of the feature defining further limits/restrictions for the product license. Each product can use a separate feature, or the same feature can be used by several products.
    If using a network license and the same feature is shared by several products, the number of instances allowed by the feature is shared between the products (e.g., 2 allowed instances enable one Charon-AXP and one Charon-SSP instance to run concurrently). If using a local license dongle and the same feature is shared by several products, the number of allowed instances is counted separately for each product.
    The parameters defined in a feature are described below in the Features section.


B) License Feature Section (one or more per license key)

Features define product specific conditions, for example expiration date and number of concurrent instances.

The following list describes these conditions:

  • Released product expiration date: for time-based licenses. Note that at the time of writing the license of Charon-AXP/VAX products will expire at the end of the day of the expiration date, the license of Charon-SSP in the early morning of the expiration day. The exact behavior of the different versions can change without prior warning. Not supported for HL-MAX dongles.
  • Runtime counter: number of license checks after which the license will be disabled. Default check interval is one hour. The counter will be decreased at the start of the emulator and then at every license check interval. Once the counter has been depleted, the license becomes invalid. This license type is typically used on licenses intended as backup licenses.
  • Login interval or Check interval: frequency of license checking during emulator execution (default 1 hour). This parameter is not visible in the show command output in older Charon product version. It is visible in the show command output of newer versions, starting with Charon-AXP/VAX 4.9 and Charon-PAR 1.10.
  • Network license: indicates that a physical license is a network license
  • Number of processes: maximum overall number of Charon instances that are allowed to run concurrently.
    This parameter is set by Stromasys to the value matching the respective customer contract. For network dongles, the maximum possible value of this parameter is determined by the type of network dongle. For example: on a NetTime10 dongle this parameter can be set to a value between 1 and 10 (depending on the customer contract). The type of dongle can be viewed via Sentinel ACC.


Example with Time-Based Parameters

The parameters below describe the following limitations to the emulator:

  • License permits running up to 2 instances of Charon at the same time.
  • License expires on May 31, 2020, or after 360 license checks (with an interval of 60 minutes between the checks).
Expiration date: 31/5/2020
Runtime counter: 360
Login interval: 60 minutes
Instances allowed: 2

If any of the conditions are no longer met (too many instances, past expiration date, all checks exhausted), the feature becomes invalid and will not allow an emulator instance (or an additional instance) to run.



© Stromasys, 1999-2024  - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.