Table of Contents
Conventions
Throughout the document(s) these conventions are followed
Notation | Description |
$ | The dollar sign in interactive examples indicates an operating system prompt for VMS. The dollar sign can also indicate non superuser prompt for UNIX / Linux. |
# | The number sign represents the superuser prompt for UNIX / Linux. |
| > | The right angle bracket in interactive examples indicates an operating system prompt for Windows command (cmd.exe). |
| Bold monospace type in interactive examples indicates typed user input. |
| Bold monospace type enclosed by angle brackets indicates command parameters and parameter values. |
| Monospace type in interactive examples, indicates command response output. |
[ ] | In syntax definitions, brackets indicate items that are optional. |
... | In syntax definitions, a horizontal ellipsis indicates that the preceding item can be repeated one or more times. |
| Italic monospace type, in interactive examples, indicates typed context dependent user input. |
The following definitions apply
| Term | Description |
|---|---|
| Host | The system on which the emulator runs, also called the Charon server |
| Guest | The operating system running on a Charon instance, for example, Tru64 UNIX, OpenVMS, Solaris, MPE or HP-UX |
Session
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:
|
The following table describes all available "session" parameters, their meaning and examples of usage:
| Parameter | Type | Value | |||||
|---|---|---|---|---|---|---|---|
| hw_model | Text string | 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:
| |||||
| configuration_name | Text string | Name of CHARON-VAX instance (unique):
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:
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 | Text string | Log file name or directory name where the log files for each CHARON-VAX execution session will be stored. If an existing directory is specified, 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:
If only a directory 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 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 number starting from 000000000 to separate log files with the same time of creation (in case if the log is being written faster than one log file per second). | |||||
| log_method | Text string |
Determines if 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 log is stored in a file that is specified explicitly with the "log" parameter. Example:
| |||||
| log_locale | Text string | 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[N], N=0 or 1 | Numeric | A number (decimal Sentinel key ID) that specifies regular (N=0) and backup (N=1) license keys to be used by CHARON-VAX.
It is also possible to specify both regular and backup key in one line:
Based on the presence of the regular and/or backup license key IDs in the configuration file, CHARON-VAX behaves as follows:
| |||||
| affinity | Text string | 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. Host CPUs are enumerated as a comma separated list of host system assigned CPU numbers:
| |||||
| n_of_io_cpus | Numeric | 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:
| |||||
| license_key_lookup_retry | Text String | 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:
where:
Examples:
|