...
Include Page KBCOMMON:DOC-GoToToc KBCOMMON:DOC-GoToToc
...
Table of Contents
| Table of Contents | ||
|---|---|---|
|
Session
General settings that control the execution of CHARON-AXP belong to an object called the "session". It is a preloaded object; therefore, only "set" commands apply.
Example:
...
The following sections describe all available "session" parameters, their meaning and examples of their usage:
...
| class | pagebreak |
|---|
hw_model
...
Virtual Alpha system hardware model to be emulated.
Use a default configuration template for each particular model as a starting point for a custom configuration. This would ensure that the parameter is set correctly.
Example:
set session hw_model="AlphaServer_ES40"
Available models are:
AlphaServer_AS400
AlphaServer_AS800
AlphaServer_AS1000
AlphaServer_AS1000A
AlphaServer_AS1200
AlphaServer_AS2000
AlphaServer_AS2100
AlphaServer_AS4000
AlphaServer_AS4100
AlphaServer_DS10
- AlphaServer_DS10L
AlphaServer_DS15
AlphaServer_DS20
AlphaServer_DS25
AlphaServer_ES40
AlphaServer_ES45
AlphaServer_GS80
AlphaServer_GS160
AlphaServer_GS320
Refer to this section to find how to set a particular Alpha model supported by CHARON-AXP.
configuration_name
...
Name of the CHARON-AXP instance (ir must be unique):
set session configuration_name="MSCDV1"
The value of this parameter is used as a prefix to the event log file name. (see below).
From the example above, the CHARON-AXP log file will have the following name:
MSCDV1-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log
xxxxxxxxx is an increasing decimal number starting from 000000000 to separate log files with the same time of creation (in case the log is being written faster than one log file per second).
It is strictly recommended to use the "configuration_name" parameter if more than one CHARON instance runs on the same server.
...
| class | pagebreak |
|---|
log
...
The log file or directory name is where the log file for each CHARON-AXP execution session is stored.
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
It is possible to overwrite the existing log file or to extend it using the "18401789411451" parameter.
Example:
|
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
CHARON-AXP automatically creates individual log files for each CHARON-AXP execution session. If the log parameter is omitted, CHARON-AXP creates a log file for each CHARON-AXP execution session in the directory where the emulator was started. In these two cases, the log rotation mode is enabled, meaning a new log file is created each time the virtual machine is started and when the log file size exceeds the one specified (see 18401789411451) and/or when the log file is older than a specified number of days (see 18401789411451).
If the "configuration_name" parameter of the session is specified, the log file name is composed as follows:
If the "configuration_name" parameter is omitted, the log file name will have the following format:
where "
Example:
The execution of the virtual machine will create a log file, named
|
...
| class | pagebreak |
|---|
log_method
...
- "append" (default)
- "overwrite"
Determines if the previous log information is maintained or overwritten.
| Info |
|---|
This parameter must be specified only in addition to “log” parameter on the same line. |
This parameter is applicable only if the CHARON-AXP log is stored to a file that is specified explicitly with the "log" parameter.
Example:
set session log="log.txt" log_method="overwrite"
log_file_size
...
If log rotation is enabled, the log_file_size parameter determines the log file size threshold at which the log is automatically rotated. Rotating log file size is multiple of 64K
- "unlimited" or "0" (default) - the feature is disabled
- "default" - default size is used (4Mb)
- <size>[KMG] - size of the current log file in bytes with additional multipliers:
K - Kilobyte - multiply by 1024
M - Megabyte - multiply by 1024*1024
G - Gigabyte - multiply by 1024*1024*1024
Example 1:
set session log_file_size="default"
Example 2:
set session log_file_size=10M
Minimum LOG File size is 64K, maximum is 1G. Setting size less than 64K effectively makes the LOG File unlimited.
...
| class | pagebreak |
|---|
log_rotation_period
...
- "default" - default value, 7 days. This values is used even if the "log_rotation_period" is not specified.
- "daily" or "1"
- "weekly" or "7"
- "never"
- <N> - in N days where N is greater than 0
If the rotation log mode is enabled this parameter controls switching to next log file based on period of time passed. If enabled the switching to next log file appears at midnight.
Example 1:
set session log_rotation_period="weekly"
Example 2:
set session log_rotation_period=14
log_flush_period
...
- <period-in-seconds>
Defines a period of flushing log to disk.
Default period is 60 seconds (it means that every minute log file is flushed to disk)
Example:
set session log_flush_period=30
...
| class | pagebreak |
|---|
license_key_id
...
license_key_id
...
A set of Sentinel Key IDs that specifies the license keys to be used by CHARON. It is also possibly to use a keyword "any" to force CHARON to look for a suitable license in all available keys if the license is not found in the specified keys.
Example:
set session license_key_id = "1877752571,354850588,any"
Based on the presence of this parameter in the configuration file, CHARON behaves as follows:
No keys are specified (the parameter is absent)
CHARON performs an unqualified search for any suitable key in unspecified order. If no key is found, CHARON exits.One or many keys are specified
CHARON performs a qualified search for a regular license key in the specified order. If it is not found, CHARON exits (if the keyword "any" is not set).
If the keyword "any" is specified then if no valid license has been found in the keys with specified ID’s all other available keys are examined for valid license as well.
| Note |
|---|
The order in which keys are specified is very important. If a valid license was found in the key which ID was not the first one specified in configuration file, then available keys are periodically re-scanned and if the key with the ID earlier in the list than the current one is found CHARON tries to find a valid license there and in case of success switches to that key. |
...
| class | pagebreak |
|---|
license_id
...
license_id
...
A set of license identifiers that specifies the licenses to be used by CHARON. This parameter is applicable only to licenses on which Stromasys placed restrictions on what products can be combined on a single license key. Please contact your Stromasys representative or VAR for more information.
Example:
set session license_id = "2718281828,314159265"
If this parameter is set, Charon considers for validation only the available licenses with license ID parameter set and equal to one of the license ID's specified in the configuration. This prioritized list corresponds to the "Product License Number" line in the Product section of the license.
license_key_lookup_retry
...
In case the CHARON-AXP license connection is not present when the guest starts up, this parameter specifies how many times CHARON-AXP will try to establish the connection and, optionally, a period of time between retries.
Syntax:
set session license_key_lookup_retry = "N [, T]"
Options:
- N - Number of retries to look for license keys.
- T - Time between retries in seconds. If not specified 60 seconds are used
Example 1:
set session license_key_lookup_retry = 1
If license key is not found during initial scan, do only one more attempt after 60 seconds.
Example 2:
set session license_key_lookup_retry = "1,30"
Same as above but retry in 30 seconds.
Example 3:
set session license_key_lookup_retry = "3,10"
If license key is not found during initial scan, do 3 more attempts waiting 10 seconds between them.
Example 4:
set session license_key_lookup_retry = "5"
If license key is not found during the initial scan, do 5 more attempts waiting 60 seconds between them.
...
| class | pagebreak |
|---|
affinity
...
Overrides any initial process affinity mask provided by the host operating system. Once specified it binds the running instance of the emulator to particular host CPUs.
Used for soft partitioning of the host CPU resources and/or for isolating host CPUs for other applications.
By default the CHARON-AXP emulator instance allocates as many host CPUs as possible. The “affinity” parameter overrides that and allows explicit specification on which host CPU the instance must run on.
| Note |
|---|
The "affinity" parameter defines the total number of host CPUs to be used both for emulated Alpha CPUs and for CHARON-AXP application itself (including the CPUs to be used for I/O - they are controlled by "n_of_io_cpus" parameter described below). |
Host CPUs are enumerated as a comma separated list of host system assigned CPU numbers:
set session affinity="0, 2, 4, 6"
...
| class | pagebreak |
|---|
...
Limits the number of emulated CPUs.
Example:
set session n_of_cpus=3
The maximum number of CPUs enabled by CHARON-AXP is specified by the license key, but cannot exceed the original hardware restrictions. See table below.
...
AlphaServer_AS400
...
| class | pagebreak |
|---|
n_of_io_cpus
...
This parameter specifies how many host CPUs CHARON-AXP must use for I/O handling. Use of the “affinity” parameter may limit the number of CPUs available.
By default the CHARON-AXP instance reserves one third of all available host CPUs for I/O processing (round down, at least one). The “n_of_io_cpus” parameter overrides that by specifying the number of CHARON I/O CPUs explicitly.
Example:
set session n_of_io_cpus=2
...
File inclusion
It is possible to include a configuration file into an existing one using the "include" command. The file extension is usually .icfg.
Format:
...
Example:
...