Versions Compared

Old Version 5

changes.mady.by.user Bruno Miretti (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Bruno Miretti (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: TOC added

Anchor
TopConfPage
TopConfPage
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

Table of Contents

Table of Contents
excludeTable 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:

set session <parameter>=<value>


The following table describes all available "session" parameters, their meaning and examples of their usage:

hw_model

Parameter

...

hw_model
TypeText string
Value

Virtual HP 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_DS15

  • AlphaServer_DS20

  • AlphaServer_DS25

  • AlphaServer_ES40

  • AlphaServer_ES45

  • AlphaServer_GS80

  • AlphaServer_GS160

  • AlphaServer_GS320

(info) Refer to this section to find how to set a particular HP Alpha model supported by CHARON-AXP.

configuration_name

Parameterconfiguration_name
TypeText string
Value

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).

(warning) It is strictly recommended to use the "configuration_name" parameter if more than one CHARON instance runs on the same server.

log

Parameterlog
TypeText string
Value

The log file or directory name is where the log file for each CHARON-AXP execution session is stored. If an existing directory is specified, 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.

It is possible to overwrite the existing log file or extend it using the "log_method" parameter. See below for details. (info) The "log_method" parameter is effective only in the case where a single log file is specified, not a directory.

Examples:

set session log="log.txt"
set session log="/CharonLogs/Logs"

If only a directory name is specified in the "log" parameter and the "configuration_name" parameter of the session is specified, the log file name will have the following format:

<configuration_name>-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log

If only a directory name is specified in the "log" parameter and the "configuration_name" parameter is omitted, the log file name will have the following format:

<hw_model>-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log

xxxxxxxxx is an increasing decimal integer, starting from 000000000 to separate log files with the same time of creation (in case the log is being created faster than one log file per second).

Note

Only existing directory can be used as a value of the "log" parameter.

Div
classpagebreak

 

log_method

Parameterlog_method
TypeText string
Value
  • "overwrite" (default)
  • "append"

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="append"

...

license_

...

key_

...

id

...

  • "all" (default)
  • "info"
  • "warning"
  • "error"

Defines the message types to be shown. The parameter is a string of comma delimited words.

Example:

set session log_show_messages="error, warning"

...

Specifies if repeated messages should be filtered or not. Possible values are "on" (default) and "off".

If the value is "on", immediately following messages with the same identifier and system error code are not listed in the log, but they are counted. When a different log message is generated, the repeat count of the earlier log message is reported with "The previous message has been repeated N times.", and the counter is cleared.

Example:

set session log_repeat_filter="on"

 
Parameter

license_key_id[N]

...

N=0 or 1

TypeNumeric
Value

An integer (decimal Sentinel Key ID) that specifies the regular (N=0) and backup (N=1) license keys to be used by CHARON-AXP.

set session license_key_id[0]=1877752571
set session license_key_id[1]=354850588

It is also possible to specify both regular and backup keys in one line:

set session license_key_id[0]=1877752571 license_key_id[1]=354850588

Based on the presence of the regular and/or backup license key IDs in the configuration file, CHARON-AXP behaves as follows:
 

  1. No keys are specified
    CHARON-AXP performs an unqualified search for any suitable key. If no key is found, CHARON-AXP exits.

  2. Both keys are specified
    CHARON-AXP performs a qualified search for a regular license key. If it is not found, CHARON-AXP performs a qualified search for backup license key. If it is not found, CHARON-AXP exits.

  3. Only regular key is specified
    CHARON-AXP performs a qualified search for a regular license key. If it is not found, CHARON-AXP performs an unqualified search for any suitable key. If none are found, CHARON-AXP exits.

  4. Only backup key is specified
    CHARON-AXP performs an unqualified search for any suitable key. If no key is found, CHARON-AXP exits.

affinity

Parameteraffinity
TypeText string
Value

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"
Div
classpagebreak

 

Anchor
n_of_cpus
n_of_cpus
n_of_cpus

Parametern_of_cpus
TypeNumeric
Value

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:

HP Alpha ModelNumber of emulated CPUs

AlphaServer_AS400

1
AlphaServer_AS8001
AlphaServer_AS10001
AlphaServer_AS1000A1
AlphaServer_AS12002
AlphaServer_AS20002
AlphaServer_AS21004
AlphaServer_AS40002
AlphaServer_AS41004
AlphaServer_DS101
AlphaServer_DS151
AlphaServer_DS202
AlphaServer_DS252
AlphaServer_ES404
AlphaServer_ES454
AlphaServer_GS808
AlphaServer_GS16016
AlphaServer_GS32032

n_of_io_cpus

Parametern_of_io_cpus
TypeNumeric
Value

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

license_key_lookup_retry

...

Parameterlicense_key_lookup_retry
TypeText String
Value

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.

 

Back to Table of Contents