Versions Compared

Old Version 1

changes.mady.by.user Copy Page Tree

Saved on

compared with

New Version 2

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: log_file_size and log_rotation_period are added

...

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

hw_model

Parameterhw_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"

log_file_size

Parameter

log_file_size

TypeText string
Value

If the rotation log mode is enabled this parameter controls switching to next log file based on size of the current file (switching appears on exiding this size).

  • "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

Examples:

set session log_file_size="default"
set session log_file_size=10M

(warning) Minimum LOG File size is 64K, maximum is 1G. Setting size less then 64K effectively makes the LOG File unlimited.

log_rotation_period

Parameterlog_rotation_period
TypeText string
Value
  • "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" or "0"
  • <N> - in N days

If the rotation log mode is enabled this parameter controls switching to next log file based on period of time passed.

Examples:

set session log_rotation_period="weekly"
set session log_rotation_period=14

(info) If enabled the switching to next log file appears at midnight

license_key_id

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.

...