...
These parameters are configured with the "set" command.
Example: Standalone VAX system with 2 virtual DSSI disks on a PAA SHAC controller
|
The emulated VAX 4000 model 106 or 108 can then boot VMS with the following command:
>>> BOOT DIA0 |
After logging into VMS, the “SHOW DEVICE D” command displays the following:
$ show devices dDevice Device Error Volume Free Trans MntName Status Count Label Blocks Count Cnt004200$DIA0: Mounted 0 DSSI01 32022 147 1004201$DIA1: Online 0 |
| Div | ||
|---|---|---|
| ||
|
HSD50 storage controller
To connect a storage controller to the virtual DSSI network, the CHARON-VAX configuration file must load at least one emulated HSD50 storage controller. In most cases one emulated HSD50 storage controller per virtual DSSI network is enough. The CHARON-VAX configuration file must supply a unique reference name for that instance. Even though this name is only valid within the configuration file, it is recommended, for clarity, to use the VMS SCSNODENAME as the instance name.The line below loads an emulated HSD50 storage controller, assigns it the instance name SCSNODE and connects it to the primary built-in DSSI controller:
load HSD50 MYDISKS dssi_host=PAA |
The HSD50 emulation has the following configuration parameters:
dssi_host
| Parameter | dssi_host |
|---|---|
| Type | Text String |
| Value | A string value that specifies the instance name of an emulated SHAC host adapter serving the virtual DSSI network.If this value is not set, CHARON-VAX will try to locate the host adapter automatically. This automatic lookup works only if the CHARON-VAX configuration has exactly one instance of an emulated SHAC host adapter. |
dssi_node_id
| Parameter | dssi_node_id |
|---|---|
| Type | Numeric |
| Value | An integer value that specifies the address of an emulated HSD50 storage controller on the virtual DSSI network.Possible values are from 0 through 7 (initially set to 0). |
scs_node_name
| Parameter | scs_node_name |
|---|---|
| Type | Text String |
| Value | A string value that specifies the SCSNODENAME of the emulated HSD50 storage controller.The string can contain as many as 6 characters. Possible characters are uppercase letters: A through Z, and the integers: 0 through 9.Initially set to the name of the emulated HSD50 controller. Therefore, the name of the emulated HSD50 controller should follow the above rules. |
scs_system_id
| Parameter | scs_system_id |
|---|---|
| Type | Numeric |
| Value | An integer value that specifies the SCSSYSTEMID of the emulated HSD50 storage controller.Initially set to an arbitrary value that is guaranteed to be unique within the running emulated VAX 4000 model 106, 108, 700 and 705 node. |
mscp_allocation_class
| Parameter | mscp_allocation_class |
|---|---|
| Type | Numeric |
| Value | An integer value that specifies the ALLOCLASS of the emulated HSD50 storage controller.Possible values are 0 through 255 (initially set to 0). |
container
| Parameter | container[N]N=0…9999 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Type | Text String | ||||||||||||
| Value | A string value that specifies the container of the storage element with MSCP unit number: N. This storage element might be either a (virtual) disk or tape. In VMS running on an emulated VAX 4000 node, these storage elements appear as HSX00 disks (DUAN:) or HST00 tapes (MUAN:).Possible values of the parameter are strings in one of the following forms:
|
media_type
| Parameter | media_type[N]N=0…9999 | |
|---|---|---|
| Type | Text String | |
| Value | Overrides the default (automatically determined) MSCP media type of the device.Syntax:
where:
Initially not specified. |
geometry
| Parameter | geometry[N]N=0…9999 | |
|---|---|---|
| Type | Text String | |
| Value | This formatted string value specifies the explicit geometry of the disk storage element with DSSI node ID: N and MSCP unit number: N. This parameter is not applicable to tape storage elements.The string format is <X>”/”<Y>[“/”<Z>] where:
If this parameter is not set, CHARON-VAX will configure the geometry based on the most probable disk type.Initially not set.The syntax above is applicable only to disk storage elements.If the container is a tape image, the following format is used:Syntax:
where:
|
use_io_file_buffering
| Parameter | use_io_file_buffering[N]N=0…9999 | |
|---|---|---|
| Type | Text String | |
| Value | Instructs CHARON-VAX to enable host operating system I/O cache on reading/writing operations.The following values are possible:
|
Note that this caching has a significant effect only in case of mapping to disk and tape containers, not physical drives.When enabled, host operating system I/O cache may significantly improve I/O performance of the virtual system. At the same time maintaining I/O cache requires additional host resources (CPU and memory) which may negatively affect overall performance of the virtual system.Initially is set to "false".Example:
Example:
load HSD50 DISKS dssi_host=PAA dssi_node_id=5 |
The configuration file below emulates a VAX 4000 Model 108 node with one HSD50 storage controller serving two disks and another instance of an HSD50 controller that serves a tape drive to the VAX over a virtual DSSI:
|
In this example we emulate two HSD50 instances. They are both connected to the same virtual DSSI bus, therefore we must assign them different DSSI node ID values.
The emulated VAX 4000 Model 108 can boot VMS with the following command:
>>> BOOT DUA0 |
After logging into VMS, the “SHOW DEVICE D” and "SHOW DEVICE M" command displays the following:
|