...
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 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).
|
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. If an existing directory is specified, CHARON-VAX / CHARON-PDP automatically creates individual log files for each CHARON-VAX / CHARON-PDP execution session. If the log parameter is omitted CHARON-VAX / CHARON-PDP creates a log file for each CHARON-VAX / CHARON-PDP 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. Note: that the "log_method" parameter is effective only in the case when a single log file is specified, not a directory. Examples:
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 is composed as follows:
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:
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).
|
...
Parameter | log_rotation_period | ||
---|---|---|---|
Type | Text string | ||
Value |
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:
|
log_repeat_filter
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 previous message has been repeated N times.", and the counter is cleared. 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 will try to establish the connection and, optionally, a period of time between retries. Syntax:
Options:
Example 1:
If license key is not found during initial scan, do only one more attempt after 60 seconds. Example 2:
Same as above but retry in 30 seconds. Example 3:
If license key is not found during initial scan, do 3 more attempts waiting 10 seconds between them. Example 4:
If license key is not found during the initial scan, do 5 more attempts waiting 60 seconds between them. |
...