...
General settings that control the execution of CHARON-VAX / CHARON-PDP belong to an object called the "session". It is a preloaded object; therefore, only "set" commands applyare necessary.
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 | |
|---|---|---|
Type | Text string | |
Value | Virtual VAX/PDP11 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:
Available models are:
|
configuration_name
Parameter | configuration_name | ||
|---|---|---|---|
Type | Text string | ||
Value | Name of the CHARON-VAX / CHARON-PDP instance (ir it must be unique):
The value of this parameter is used as a prefix to the event log file name . (see below). From the example above, the CHARON-VAX / CHARON-PDP log file will have the following name:
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 "| Div | ||
|---|---|---|
| ||
log
| Parameter | log | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Type | Text string | ||||||||||||||||||||||||||||||
| Value | The log file or directory name is where the log file for each CHARON-VAX / CHARON-PDP execution session is stored.
|
...
| Parameter | log_method | |||
|---|---|---|---|---|
| Type | Text string | |||
| Value |
Determines if the previous log information is maintainedor overwritten.
This parameter is applicable only if the CHARON-VAX / CHARON-PDP log is stored to a file that is specified explicitly with the "log" parameter. Example:
|
...
| Parameter | log_file_size | ||
|---|---|---|---|
| Type | Text 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.
Examples:
|
log_rotation_period
| Parameter | log_rotation_period | ||
|---|---|---|---|
| Type | Text string | ||
| Value |
If the rotation log mode is enabled, this parameter controls switching to the next log file based on a period of time passed. If enabled, the switching to the next log file appears occurs at midnight. Examples:
|
...
| Parameter | log_repeat_filter | |
|---|---|---|
| Type | Text 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 entry "The previous message has been repeated N times." , and the counter is cleared. Example:
|
...
| Parameter | license_key_id[N], N=0 or 1 | ||
|---|---|---|---|
| Type | Numeric | ||
| Value | An integer (decimal Sentinel Key ID) that specifies the regular (N=0) and backup (N=1) license keys to be used by CHARON-VAX / CHARON-PDPthe CHARON VM.
It is also possible to specify both regular and backup keys in one line:
Based on the presence of the regular and/or backup license key IDs in the configuration file, CHARON-VAX / CHARON-PDP behaves as follows:
|
affinity
| Parameter | affinity | |||
|---|---|---|---|---|
| Type | Text 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-VAX / CHARON-PDP 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.
Host CPUs are enumerated as a comma separated list of host system assigned CPU numbers:
|
...
| Parameter | n_of_io_cpus | |
|---|---|---|
| Type | Numeric | |
| Value | This parameter specifies how many host CPUs CHARON-VAX / CHARON-PDP must use for I/O handling. Use of the “affinity” parameter may limit the number of CPUs available. By default the CHARON -VAX / CHARON-PDP instance VM 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:
|
...
| Parameter | license_key_lookup_retry | |||||
|---|---|---|---|---|---|---|
| Type | Text String | |||||
| Value | In case the CHARON-VAX / CHARON-PDP license connection is not present when the guest starts up, this parameter specifies how many times CHARON-VAX / CHARON-PDP the CHARON VM will try to establish the connection and, optionally, a period of time between retries. Syntax:
Options:
Example 1:
If the license key is not found during initial scan, do only one more attempt after 60 seconds is performed. Example 2:
Same as above but retry in 30 seconds. Example 3:
If the license key is not found during initial scan, do 3 more attempts waiting 10 seconds between them. Example 4:
If the license key is not found during the initial scan, do 5 more attempts waiting 60 seconds between them. |
| Div | ||
|---|---|---|
| ||
File inclusion
It is possible to include a configuration file into an existing one using the "include" command. File The file extension is usually .icfg.
Format:
include |
"file. |
icfg" |
Example:
include "c:\charon\commonpart.icfg" |
The configuration template files are defined to use the "configuration_name.icfg" configuration file which is used by the CHARON Virtual Machines Manager. If you use an existing configuration file, including this file is not necessary.