...
General settings that control execution of CHARON-VAX belong to an object callled "session". It is a preloaded object; therefore, only "set" commands apply.
Example:
set session <parameter>=<value> |
The following tables describe all available "session" parameters, their meaning and examples of usage:
hw_model
| Parameter | hw_model |
|---|
| Type | Text string |
|---|
| Value | Virtual VAX 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="VAX_6610" |
The models are: MicroVAX_3100_Model_96 MicroVAX_3100_Model_98 MicroVAX_3600 MicroVAX_3900 MicroVAX_II VAXserver_3600 VAXserver_3600 VAXserver_3600_128 VAXserver_3600_512 VAXserver_3900 VAXserver_3900_128 VAXserver_3900_512 VAX_4000_Model_106 VAX_4000_Model_108 VAX_4000_Model_700 VAX_4000_Model_705 VAX_6000_Model_310 VAXstation_4000_Model_90 VAX_6610 VAX_6620 VAX_6630 VAX_6640 VAX_6650 VAX_6660
|
|---|
configuration_name
| Parameter | configuration_name |
|---|
| Type | Text string |
|---|
| Value | Name of CHARON-VAX instance (unique): set session configuration_name="MSCDV1" |
The value of this parameter is used as prefix to the event log file name when multiple log files are configured (see below). From the example above, the CHARON-VAX 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). |
|---|
log
| Parameter | log |
|---|
| Type | Text string |
|---|
| Value |
|---|
Log name or directory name is where the log |
files file for each CHARON-VAX execution session |
will be stored. If an existing directory is specified, is stored. | Panel |
|---|
| borderColor | #3AAADC |
|---|
| bgColor | #FFFFFF |
|---|
| titleColor | #FFFFFF |
|---|
| titleBGColor | #3AAADC |
|---|
| title | Log specified as a file name |
|---|
| It is possible to overwrite the existing log file or to extend it using the "log_method" parameter.  The "log_method" parameter is effective only when a single log file is specified, not a directory.
Example: set session log="/charon/vax4106prod.log" |
|
| Panel |
|---|
| borderColor | #0062AB |
|---|
| bgColor | #FFFFFF |
|---|
| titleColor | #FFFFFF |
|---|
| titleBGColor | #0062AB |
|---|
| title | Log specified as a directory |
|---|
| CHARON-VAX automatically creates individual log files for each CHARON-VAX execution session. If the log parameter is omitted, CHARON-VAX creates a log file for each CHARON-VAX execution session in the directory where the emulator was started. |
|
Examples:
set session log="log.txt" |
set session log="/charon/logs" |
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). A symbolic link 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 |
|
only a directory is specified in "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 |
where "xxxxxxxxx |
|
is " is an increasing decimal |
|
number integer, starting from 000000000 to separate log files with the same time of creation (in case |
|
if written created faster than one log file per second). |
|
| Note |
|---|
 Only existing directory can be
|
|
used as a value of the "log" parameterspecified. If the directory specified does not exist, this will be considered as a flat file.
Example: set session configuration_name="vax4106prod"
set session log="/charon/logs"
|
The execution of the virtual machine will create a log file, named /charon/logs/vax4106prod-2016-10-13-10-00-00-000000000.log (for example) and a symbolic link named /charon/logs/vax4106prod.log pointing to this file. The link will be updated when the log rotation will occur. |
|
log_method
| Parameter | log_method |
|---|
| Type | Text string |
|---|
| Value | - "overwrite" (default)
- "append"
Determines if previous log information is maintained. | Info |
|---|
| This parameter must be specified only in addition to “log” parameter on the same line. |
This parameter is applicable only if the CHARON-VAX log is stored in 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 |
|---|
| 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.- "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
|
Minimum LOG File size is 64K, maximum is 1G. Setting size less then 64K effectively makes the LOG File unlimited. |
|---|
log_rotation_period
| Parameter | log_rotation_period |
|---|
| Type | Text 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. If enabled the switching to next log file appears at midnight. Examples: set session log_rotation_period="weekly"
|
set session log_rotation_period=14
|
If enabled the switching to next log file appears at midnight |
|---|
license_key_id
| Parameter | license_key_id[N] N=0 or 1 |
|---|
| Type | Numeric |
|---|
| Value | A number (decimal Sentinel key ID) that specifies regular (N=0) and backup (N=1) license keys to be used by CHARON-VAX. set session license_key_id[0]=1877752571
set session license_key_id[1]=354850588 |
It is also possible to specify both regular and backup key 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-VAX behaves as follows:
No keys are specified
CHARON-VAX performs an unqualified search for any suitable key. If no key is found, CHARON-VAX exits. Both keys are specified
CHARON-VAX performs a qualified search for a regular license key. If it is not found, CHARON-VAX performs a qualified search for backup license key. If it is not found, CHARON-VAX exits. Only regular key is specified
CHARON-VAX performs a qualified search for a regular license key. If it is not found, CHARON-VAX performs an unqualified search for any suitable key. If none are found, CHARON-VAX exits. Only backup key is specified
CHARON-VAX performs an unqualified search for any suitable key. If no key is found, CHARON-VAX exits.
|
|---|
license_key_lookup_retry
| Parameter | license_key_lookup_retry |
|---|
| Type | Text String |
|---|
| Value | In case the CHARON-VAX license connection is not present at guest statup, this parameter specifies how many times CHARON-VAX will try to reestablish the connection and, optionally, a period of time between retries. Syntax: set session license_key_lookup_retry = "N [, T]" |
where: - N - Number of retries looking for license key (or keys)
- T - Time between retries in seconds. If not specified 60 seconds is 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 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 initial scan, do 5 more attempts waiting 60 seconds between them. |
|---|
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.Can be used for soft partitioning host CPU resources and/or for isolating host CPUs for other applications.By default CHARON-VAX 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. | Note |
|---|
| The "affinity" parameter defines the total number of host CPUs to be used both for emulated VAX CPUs and for CHARON-VAX / CHARON-PDP 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" |
|
|---|
n_of_io_cpus
| Parameter | n_of_io_cpus |
|---|
| Type | Numeric |
|---|
| Value | This parameter specifies how many host CPUs CHARON-VAX must use for I/O handling. Use of the “affinity” parameter may limit the number of CPUs available.By default the CHARON-VAX instance reserves one third of 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 |
|
|---|
...
Back to Table of Contents