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 |
Introduction
This chapter describes in detail all configuration parameters of the devices emulated by CHARON-VAX for Linux, with corresponding examples of their loading and parameters.
Emulated devices are loaded with "load" command (if device has not been already loaded) and parameters are made active the "set"command. It is possible to specify parameters directly in the "load" command.
Example:
load RQDX3/RQDX3 DUA set DUA container[0]="/charon/disks/user.vdisk" |
In this example, an instance of an RQDX3 controller is loaded with a name "DUA". Its first unit ("container[0]") is mapped to "/charon/disks/user.vdisk" disk image.
The Controller name is accompanied with a "/<module name>". The module name is a CHARON-VAX component that specifies the controller load module. Its name can be the same as the loaded controller, but that is not required. Once a module name is specified there is no need to specify it again for additional references of the same controller..
Details of CHARON-VAX configuration