General Settings
- Copy Page Tree
- Bruno Miretti (Deactivated)
Session
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 apply.
Example:
|
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).
|
It is strictly recommended to use the "
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). |
log_method
| Parameter | log_method | |
|---|---|---|
| Type | Text string | |
| Value |
Determines if the previous log information is maintained. This parameter must be specified only in addition to “log” parameter on the same line. 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:
|
log_locale
| Parameter | log_locale | |
|---|---|---|
| Type | Text string | |
| Value | Sets the language used in the message database. So far the following values are supported:
If an unsupported value is specified, “English” will be used. Example:
|
license_key_id
| 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-PDP.
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:
|
n_of_io_cpus
| 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 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:
|
license_key_lookup_retry
| 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:
Examples: 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. |
© Stromasys, 1999-2024 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.