Versions Compared

Old Version 7

changes.mady.by.user Bruno Miretti

Saved on

compared with

New Version 8

changes.mady.by.user Bruno Miretti

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Log rotation mode updated with more details

...


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 VM (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 VM 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 VM runs on the same server.

log

VM If an existing directory is specified,CHARON VM automatically creates individual log files for each CHARON-AXP execution session. If the log parameter is omitted CHARON VM creates a log file for each CHARON VM execution session in the directory where the emulator was started. See below for details. in the case where Examples"log.txtset session log="Logs"If only a directory name is specified in the "log" parameter and will have the following format only a directory name is specified in "log" parameter and the  is used as a value of the "log" parameter
Parameterlog
TypeText string
Value

The log file or directory name is where the log file for each CHARON

-AXP execution session is stored.

Panel
borderColor#3AAADC
bgColor#FFFFFF
titleColor#FFFFFF
titleBGColor#3AAADC
titleLog specified as a file name

It is possible to overwrite the existing log file or to extend it using the "log_method" parameter.

(info) The "log_method" parameter is effective only

when a single log file is specified, not a directory.

Example:

set session log=
"
C:\Charon\
es40prod.log"
Panel
borderColor#0062AB
bgColor#FFFFFF
titleColor#FFFFFF
titleBGColor#0062AB
titleLog specified as a directory

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 log_file_size) and/or when the log file is older than a specified number of days (see log_rotation_period).

(info) A shortcut located in the same directory will be created, pointing to the active log file. Its name is based on the hw_model parameter or the configuration_name parameter if specified.

If the "configuration_name" parameter of the session is specified, the log file name

is composed as follows:

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

If

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

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

(warning) Only existing directory can be

specified. If the directory specified does not exist, this will be considered as a flat file. No trailing backslash character is allowed.

Example:

set session configuration_name="es40prod"

set session log="C:\Charon\Logs"

The execution of the virtual machine will create a log file, named C:\Charon\Logs\es40prod-2016-10-13-10-00-00-000000000.log (for example) and a shortcut named C:\Charon\Logs\es40prod.log pointing to this file. The shortcut will be updated when the log rotation will occur.

log_method

Parameterlog_method
TypeText string
Value
  • "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 VM log is stored to a file that is specified explicitly with the "log" parameter.

Example:

set session log="log.txt" log_method="append"

log_show_messages

Parameterlog_show_messages
TypeText string
Value
  • "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"

log_file_size

Parameter

log_file_size

TypeText string
Value

If log rotation is enabled, the log_file_size parameter determines the log file size threshold at which the log is automatically rotated.

  • "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 value 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. If enabled the switching to next log file appears at midnight

Examples:

set session log_rotation_period="weekly"

set session log_rotation_period=14

log_repeat_filter

Parameterlog_repeat_filter
TypeText string
Value

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


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

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 VM behaves as follows:
 

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

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

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

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



...