Page Comparison

...

Creation of CHARON VM configuration

Once you have created When a CHARON Virtual Machine (VM) in CHARON Virtual Machine Manager using some template you should update this sample template is created from a template using the CHARON Virtual Machines Manager, it has to be updated to meet the desired configuration of your HP Alpha.

This configuration is represented as a text file ("configuration file") containing some specific keywords to define the HP Alpha main settings such as amount of memory, number of CPUs, peripheral devices as well as specifics of CHARON VM executions such as name of VM log file, number of host CPUs used for emulation, etc.

To change the configuration file, run open the CHARON Virtual Machine Machines Manager from its shortcut on Desktop / Start menu or from the tray menu item, select the target CHARON VM and either press the "Change VMEdit Configuration" button or select the "VM Configuration" tab:

Image Removed

In the appearing dialog press the "Edit Configuration file" button:

Image Removed

Edit the CHARON VM configuration using the default text editor:

Image Removed

...

Image Added

Notepad will be used to edit the configuration file:

Image Added

VAX/PDP11 model specification

...

You must leave this line untouched.

If you create the CHARON VM configuration file from scratch, it must be the very first uncommented line in the configuration file.

...

Configuration name

The next configuration statement is the "Configuration name" option:

You can optionally uncomment this line to differentiate this CHARON VM instance from all others in a multi-instance environment. The configuration name can be any label that is meaningful.. If the virtual machine has been created using an existing template, the configuration name is defined in the configuration_name.icfg file otherwise it is defined directly in the configuration file using the "set session configuration_name = <...>" syntax:

Notes:

• The configuration name is reported in the log file and is used to set the log file name for rotating

...

• log (see explanations further

...

• )

...

• .

See example below with configuration name set to: MicroVAX_3100_Model_98

Back to Table of Contents

Log file parameters

Execution of CHARON VM creates one log file or a set of log files reflecting the progress of its start-up and ongoing operation - start and end time of execution, system information, license and configuration details, warnings, reports on problems that may occur, etc. In case of possible problems either with the running CHARON VM or the emulated system configuration (such as the absence or malfunction of certain devices), the log file(s) is the primary source to be analyzed for troubleshooting. If it becomes necessary to contact Stromasys for support, the configuration and log files will be requested to begin problem resolution.

Here is an example of a CHARON VM log file:

...

• Changing the configuration name in the "configuration_name.icfg" file does not change the name of the virtual machine at Virtual Machines Manager level.
• The "configuration_name.icfg" file can be found in the home directiory of the VM. Select the target VM, open "VM Configuration" tab and press "Explore" button.

The configuration name can be any label that is meaningful.

Example:

It is possible to specify a configuration name containing spaces, in this case use quotation marks:

Log file parameters

The execution of a CHARON VM creates one log file or a set of log files reflecting the progress of its start-up and ongoing operation: start and end time of execution, system information, license and configuration details, warnings, reports on problems that may occur, etc. In case of problems with either the running CHARON VM or the emulated system configuration (such as the absence or malfunction of certain devices), the log file is the primary source to be analyzed for troubleshooting.

If it becomes necessary to contact Stromasys for support, the configuration and log files will be requested to begin the problem resolution.

Here is an example of a CHARON VM log file:

The next group of parameters defines the name of the CHARON VM log file and how CHARON VM will use it:

...

set session log_method = append
#set session log_method = overwrite
#set session log = "MicroVAX_3600.log"

Rotating log (default)

By default CHARON utilizes a so-called "rotating log". This means that a new default log file is always created each time CHARON VM starts and can switch to another log file if the size of the log file exceeds 64Kb.

This mode is turned on if all the log parameters above are disabled (commented out) or the "session_log" parameter is pointing to a directory rather than to a file. If a directory is specified, the log files will be created in that directory.

Names of the rotating log files are composed as follows:

...

configuration_name-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log

If the "Configuration name" parameter described before is omitted (commented out), the log name has the following format instead:

...

hw_model-YYYY-MM-DD-hh-mm-ss-xxxxxxxxx.log

Note that "xxxxxxxxx" is an increasing decimal number starting from "000000000" to separate log files with the same time of creation.

Single log

Alternatively it is possible to use just a single log file. Uncomment the "set session log" line and specify the desired CHARON VM log file name. Optionally, a path can be added to the log file name. If the path is not specified, the log file is created in the directory from where the guest (emulated machine) is started.

The log file can be extended ("log_method = append") or overwritten ("log_method = overwrite") by CHARON VM.

Below is a specification of a CHARON VM log file located in the "C:\My logs" directory which will be overwritten each time CHARON VM starts:

...

set session log_method = overwrite
set session log = "C:\My logs\my_vax.log"

Back to Table of Contents 

TOY, ROM and EEPROM containers

The next objects to be configured are TOY, ROM and EEPROM containers (their presence depends on the VAX/PDP11 model). It is always recommended to enable them. If a container file of the given name does not exist, CHARON VM will create it. It is recommended to specify the path for each file so that time and console parameters will be kept whatever the current directory is when starting the guest.

TOY means "Time of Year"; its container records time, date and some console parameters while CHARON VM is not running. To enable, uncomment the following line:

The ROM container stores an intermediate state of the Flash ROM and some console parameters. So its container is also recommended to keep uncommented:

EEPROM stores the NVRAM content, so its container is also recommended to keep uncommented:

Back to Table of Contents

KW11 timer

PDP11/93 and PDP11/94 emulators require the KW11 system timer to be configured:

Just uncomment the line corresponding to the frequency used in the RSX11/RT11 systems to be migrated.

Back to Table of Contents

ACE mode

The next setting indicates whether CHARON VM will use Advanced CPU Emulation (ACE) mode:

...

#set cpu ace_mode = false
#set cpu ace_mode = true

 Note that ACE significantly speeds up CHARON execution.

Uncomment the desired mode. ACE uses a significant amount of host memory for its normal operation. Check the host resources before enabling.

If the "ace_mode" parameter is commented out, CHARON will set ACE mode according to your license settings. "Charon-xx/Plus" products have ACE mode enabled by default.

Back to Table of Contents

Emulated memory (RAM) size

The next parameter defines the amount of host memory the chosen CHARON VM model reserves for the emulation:

The amount of RAM is specified in MB. It cannot exceed or be lower than certain values specific for each VAX/PDP11 model. It is very important to keep the listed predefined increment between possible memory values.

...

The following table shows all the parameters:

...

It is possible to leave the RAM line commented out. In this case the model's default RAM amount is used. 

Note that in some particular orders your license may restrict the maximum RAM amount of each VAX/PDP11 model.

Back to Table of Contents

...

Console

Mapping to system resources

The next step is the specification of the VAX/PDP11 console (OPA0) serial line:

...

The goal of this configuration step is to tell CHARON VM what host device to use as the virtual system console. The following options are available:

...

The default setting is:

...

Note that the VAX 4000 and MicroVAX 3100 models have a 4-line QUART adapter onboard, so their configuration for the console line looks a bit different:

The next group of parameters defines the name of the CHARON VM log file and how the CHARON VM will use it:

Rotating log (default)

By default the CHARON utilizes a so-called "rotating log" method. This means that a new default log file is always created each time the CHARON VM starts and if the size of the log file exceeds 64Kb (previous log files are kept).

This mode is turned on if all the log parameters above are disabled (commented out) or the "session_log" parameter is pointing to a directory rather than to a file. If a directory is specified, the log files will be created in that directory.

The names of the rotating log files are composed as follows:

If the "Configuration name" parameter described before is omitted (commented out), the log name has the following format instead:

Note that "xxxxxxxxx" is an increasing decimal number starting from "000000000" to separate log files with the same time of creation.

The "log" parameter, if specified, must correspond to an existing folder.

If the path is not specified, the log file is created in the "Home directory" mentioned in the VM Configuration tab of the CHARON Virtual Machine Manager.

Single log

Alternatively it is possible to use a single log file. Uncomment the "set session log" line and specify the desired log file name. Optionally, a path can be added to the log file name.

If the path is not specified, the log file is created in the "Home directory" mentioned in the VM Configuration tab of the CHARON Virtual Machine Manager.

The log file can be extended specifying "log_method = append" (*recommended for reporting issues*) or overwritten, specifying "log_method = overwrite".

Below is a specification of a CHARON VM log file located in the "C:\My logs" directory which will be appended each time the CHARON VM starts:

TOY, ROM and EEPROM containers

The TOY, ROM and EEPROM containers have to be configured. Their presence depends on the VAX/PDP11 model. It is always recommended to enable them. If a container file of the given name does not exist, starting the CHARON VM will create it.

TOY means "Time of Year". Its container records time, date and some console parameters while the CHARON VM is not running.  It is highly recommended to define and activate this container:

The ROM container stores an intermediate state of the Flash ROM and some console parameters. It is highly recommended to define and activate this container:

EEPROM stores the NVRAM content. It is highly recommended to define and activate this container:

KW11 timer

PDP11/93 and PDP11/94 emulators require the KW11 system timer to be configured:

Uncomment the line corresponding to the frequency used in the RSX11/RT11 systems to be migrated if needed.

ACE mode

The next setting indicates whether the CHARON VM will use the Advanced CPU Emulation (ACE) mode:

 Note that ACE significantly speeds up CHARON execution.

Uncomment the desired mode. ACE uses a significant amount of host memory for its normal operation. Check the host resources before enabling.

The "ace_mode" mode is license dependent, the "Charon-xx/Plus" products have ACE mode enabled by default.

Emulated memory (RAM) size

The next parameter defines the amount of host memory the CHARON VM reserves for the emulation:

The amount of RAM is specified in MB. It cannot exceed or be lower than certain values specific for each VAX/PDP11 model. It is very important to keep the listed predefined increment between possible memory values.

The following table shows all the parameters:

It is possible to leave the RAM line commented out. In this case the model's default RAM amount is used. 

Note that in some particular orders your license may restrict the maximum RAM amount of each VAX/PDP11 model.

Console

Mapping to system resources

The next step is the specification of the VAX/PDP11 console (OPA0) serial line:

In case of VAX 4000 and MicroVAX 3100 models, it is possible to configure up to 4 independent console lines: OPA0, TTA0, TTA1 and TTA2. The main one is OPA0.

Note there are a number of additional parameters for CHARON VM serial lines configuration. Follow this link for details.

Exit on pressing F6 button

It is also recommended to set a hot key to stop the guest from the console in addition to the system tray icon:

This line provides CHARON VM the ability to exit by pressing the "F6" button.

Back to Table of Contents

Disk subsystem

The next step is configuration of the disk subsystem and mapping it to system resources using the samples given in the template configuration files.

CHARON supports MSCP, DSSI, CI and SCSI disk controllers.

The examples below are for MSCP and SCSI controllers only. DSSI controllers are discussed in details in the following section, CI controllers - in this section.

...

MSCP disk controllers (RQDX3, KDB50, KDM70)

Below is a typical configuration sample for MSCP disk controller RQDX3:

...

#load RQDX3 DUA

#set DUA container[0]="<file-name>.vdisk"
#set DUA container[1]="\\.\PhysicalDrive<N>"
#set DUA container[2]="\\.\PhysicalDrive(DevID = <XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX>)"
#set DUA container[3]="\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
#set DUA container[4]="\\.\CdRom<N>"
#set DUA container[5]="<file-name>.iso"
#set DUA container[6]="\\.\A:"
#set DUA container[7]="\\.\H:"

#load RQDX3 DUB address=...
#load RQDX3 DUC address=...

The first line ("load RQDX3 DUA") loads disk controller RQDX3 with name DUA, followed by 6 lines showing different ways of mapping to the host resources:

...

• "<file-name>.vdisk"
  These files can be created from scratch with "MkDisk" utility. Data and OS disks backups are transferred from the original system via tapes or network and restored into these container files.

  Mapping may also include the full path (recommended), for example: "C:\My disks\my_boot_disk.vdisk" 

  Example:

  set DUA container[0]="my_bootable_disk.vdisk"

  .
  

  Warning
  Using compressed folders to store virtual disks and tapes is not supported

  .
  

...

.

...

DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).

Example:

...

...

The goal of this configuration step is to tell the CHARON VM what host device to use as the virtual system console. The following options are available:

The default setting is:

Note that the VAX 4000 and MicroVAX 3100 models have a 4-line QUART adapter onboard, so their configuration for the console line looks a bit different:

When using the VAX 4000 and MicroVAX 3100 models, it is possible to configure up to 4 independent console lines: OPA0, TTA0, TTA1 and TTA2. The main one is OPA0.

Note that additional parameters for the CHARON VM serial lines configuration can be added. Follow this link for details.

Exit on pressing F6 button

It is recommended to set a hot key to stop the VM from the console (when the console is accessed remotely for example):

This line allows the CHARON VM to be stopped by pressing the "F6" key.

Disk subsystem

The disk subsystem and the mapping to the system resources can be done using the samples given in the template configuration files.

CHARON supports MSCP, DSSI, CI and SCSI disk controllers.

The examples below are for MSCP and SCSI controllers only. DSSI controllers are discussed in details in the following section, CI controllers - in this section.

MSCP disk controllers (RQDX3, KDB50, KDM70)

Below is a typical configuration sample for the MSCP disk controller RQDX3:

#load RQDX3 DUA

#set DUA container[0]="<file-name>.vdisk"
#set DUA container[1]="\\.\PhysicalDrive<N>"
#set DUA container[2]="\\.\PhysicalDrive(DevID =

...

 <XXX-

...

XXXX-

...

XXXX-

...

XXXX-

...

XXXX-

...

XXXX-

...

.

Mapping to iSCSI disks.

XXXX-XXXX>)"
#set DUA container[3]="\\.\PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"

...

Example:

...

...

#set DUA container[4]="\\.\CdRom<N>"
#set DUA container[5]="<file-name>.iso"
#set DUA container[6]="\\.\A:"
#set DUA container[7]="\\.\

...

...

Mapping to CD-ROM device.

...

H:"

#load RQDX3 DUB address=...
#load RQDX3 DUC address=...

The first line ("load RQDX3 DUA") loads disk controller RQDX3 with name DUA, followed by 6 lines showing different ways of mapping to the host resources:

• Mapping to the file representing a physical disk of the VAX/PDP11 system (disk image).

  • "<file-name>.vdisk"
    These files can be created from scratch with "MkDisk" utility. Data and OS disks backups are transferred from the original system via tapes or network and restored into these container files.

    Mapping may also include the full path (recommended), for example: "C:\My disks\my_boot_disk.vdisk" 

    Example:

    set DUA container[40]="\\.\CdRom0"my_bootable_disk.vdisk"

    .

    Warning
    Using compressed folders to store virtual disks and tapes is not supported

    .
    

• Mapping to an ISO file for reading distribution CD-ROM imagephysical disk.

  • "<file-name>.iso"Mapping may also include the full path (recommended), for example: "C:\My disks\vms_distributive.iso"\\.\PhysicalDrive<N>"
    Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake. These disks must not be formatted by the host OS.  
    
    Example:
    

    set DUA container[51]="vms_distributive.iso"

    .

  Mapping to Floppy drive. 
  

  • "\\.\A:"

    Example:

    "\\.\PhysicalDrive1"

    .

• Mapping to physical disk by its WWID.
  
  • "\\.\PhysicalDrive(DevID = <XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX>)"
    Be careful not to destroy all the information from the disk dedicated to CHARON VM by mistake. These disks must not be formatted by the host OS.
    

    DevID addresses the target physical disk by its WWID (hexadecimal 128-bit identifier assigned to the disk drive by its manufacturer/originator).

    Example:

    Div class small set DUA container[ 6 2]="\\.\ A: PhysicalDrive(DevID= 6008-05F3-0005-2950-BF8E-0B86-A0C7-0001)"

    .

•  Mapping to some other type of drive, for example magneto-optical drive.  

  "\\.\<N>:"

  Example:
  

  set DUA container[6]=

  Mapping to iSCSI disks.

  • "\\.\

    H:"

    .
    

Numbers in the square brackets represent unit numbers associated with each container of the MSCP controller. For example, the 3rd "set DUA" line of the configuration sample above creates disk "DUA2". The maximum unit number allowed is 9999, significantly more than the original hardware provided.

It is possible to load several RQDX3 controllers DUB, DUC, etc. (see lines 6-7, above) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX console to determine the addresses. Please refer to specific HP documentation for further information.

Please also refer to HP documentation for information on placement of additional KDM70 controllers on an XMI bus (VAX 6000 models) and additional KDB50 controllers on a BI bus (VAX 6310).

Note that the KDM70 controller is capable of mapping to files representing tapes (tape images) and physical tape devices:

...

• • PhysicalDrive(iScsiTarget = <iSCSI target>, LUN = <LUN number>)"
    iScsiTarget addresses the disk by its iSCSI target name. LUN specifies LUN on connected iSCSI disk.

    Example:

    Div class small set DUA container[3]="\\.\PhysicalDrive(iScsiTarget= iqn.2008-04:iscsi.charon-target-test1, LUN= 1)"

     

• Mapping to CD-ROM device.

  • "\\.\CdRom<N>"

    Example:

    set DUA container[4]="\\.\CdRom0"

    .

• Mapping to an ISO file for reading distribution CD-ROM image.

  • "<file-name>.iso"

    Mapping may also include the full path (recommended), for example: "C:\My disks\vms_distributive.iso"

    Example:
    

    set DUA container[5]="vms_distributive.iso"

    .

• Mapping to Floppy drive. 
  

  • "\\.\A:"

    Example:
    

    set DUA container[6]="\\.\A:"

    .

•  Mapping to some other type of drive, for example magneto-optical drive.  

  • "\\.\<N>:"

    Example:
    

    set DUA container[6]="\\.\

...

• • H:"

...

Follow this link for details of (T)MSCP controllers configuration.

Back to Table of Contents

...

SCSI controller NCR53C94

The VAX 4000 and MicroVAX 3100 have an NCR53C94 SCSI controller onboard for support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.

Below is a typical configuration template for a preloaded "PKA" NCR53C94 SCSI controller:

# Mapping to disk image
load virtual_scsi_disk pka_0 scsi_bus=pka scsi_id=0
set pka_0 container="<file-name>.vdisk"

# Mapping to physical disk
load virtual_scsi_disk pka_1 scsi_bus=pka scsi_id=1
set pka_1 container[0]="\\.\PhysicalDrive<N>"
set pka_1 container[1]="\\.\PhysicalDrive(DevID =<XXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX>)"

# Mapping to SCSI device not recognized by Windows
load physical_scsi_device pka_2 scsi_bus=pka scsi_id=2
set pka_2 container="\\.\Scsi<N>:<X>:<Y>:<Z>"

# Mapping to host CD-ROM or DVD-ROM
load virtual_scsi_cdrom pka_3 scsi_bus=pka scsi_id=3
set pka_3 container="\\.\CdRom<N>"

# Mapping to *.ISO image
load virtual_scsi_cdrom pka_4 scsi_bus=pka scsi_id=4
set pka_4 container="<file-name>.iso"

...

• • .
    

The numbers in the square brackets represent the unit numbers associated with each container of the MSCP controller. For example, the 3rd "set DUA" line of the configuration sample above creates disk "DUA2". The maximum unit number allowed is 9999, significantly more than the original hardware provided.

It is possible to load several RQDX3 controllers DUB, DUC, etc. (see lines 6-7, above) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX console to determine the addresses. Please refer to specific HP documentation for further information.

Please also refer to the HP documentation for information on placement of additional KDM70 controllers on an XMI bus (VAX 6000 models) and additional KDB50 controllers on a BI bus (VAX 6310).

Note that the KDM70 controller is capable of mapping to files representing tapes (tape images) and physical tape devices:

Follow this link for details of (T)MSCP controllers configuration.

SCSI controller NCR53C94

The VAX 4000 and MicroVAX 3100 models have an NCR53C94 SCSI controller on board for the support of different types of SCSI devices including disks and tapes. Optionally a second controller can be added.

Below is a typical configuration template for a preloaded "PKA" NCR53C94 SCSI controller:

Note that NCR53C94 SCSI controller mapping to system resources is done via specific auxiliary objects:

...

Note that NCR53C94 SCSI controller mapping to system resources is done via specific auxiliary objects:

...

In the example above the "pkb_0" virtual SCSI device uses "PKB" controller by specifying a parameter "scsi_bus=pkb"

...

Follow this link for details of NCR53C94 SCSI controller controllers configuration.

...

Tape subsystem

Some MSCP and SCSI controllers support tape devices. CHARON also emulates specific MSCP tape devices such as TQK50 and TUK50.

Follow this link for more details of (T)MSCP controllers configuration.

...

Example statements to configure a TQK50 controller are shown below:

The first line ("load TQK50 MUA") loads a tape controller TQK50 with a name of and names it MUA. The following 2 lines demonstrate different ways of mapping to host resources:

Numbers in the square brackets represent unit numbers associated with each container of the TQK50 controller. For example, the 2nd "set MUA" line of the configuration sample above creates tape drive the "MUA1" tape drive. The maximum unit number allowed is 9999, significantly more than the original hardware provided

...

The first line loads a UNIBUS BI adapter "DWBUA". Then configure Configure then the "TUK50" tape controller the same way as the TQK50.

...

Serial Lines

CHARON supports the following serial lines controllers: CXA16, CXB16, CXY08, DHQ11, DHV11, DZV11, DZQ11, DL11, DLV11, DZ11, DHW42-AA, DHW42-BA and DHW42-CA.

...

The first 5 lines of the example above demonstrate above are example given for loading serial line controllers of different types. The name of the controller (in this example) will be "TXA".

Once the controller is loaded it can be mapped to system resources (lines 6-11). The following options are available:

Look at the line "set TXA line[0]=TXA0" in the example. This one and the following lines of similar syntax map the loaded virtual controller ("TXA") to instances of the host serial lines ("TXA<N>").

The number of possible serial lines possible for each controller depends on its type and corresponds to the HP specification on for a given controller.

It is possible to load several CXA16, CXB16, CXY08, DHQ11, DHV11, DZV11, DZQ11, DL11, DLV11 and DZ11 controllers (see the lines 12-16) by configuring specific addresses for them on the Qbus. Use the "CONFIGURE" utility available on the VAX/PDP11 console to determine the addresses. Please refer to specific HP documentation for further information.

The VAX 4000 and MicroVAX3100 models support DHW42-AA, DHW42-BA and DHW42-CA serial lines adapters:

...

Note that additional parameters exist for CHARON VM serial lines configuration , follow can be added. Follow this link for details.

...

Networking

...

In the example above the first line loads DELQA virtual adapter with a name "XQA"; the following 2 lines map it to host network interface having a name "Charon" ("connection" is a key word). Note that the

The mapping is performed in 2 steps:

1. A mapping object "packet_port" with a name "XQA0" is loaded and connected to host interface having a name "Charon" , so the CHARON VM will use this interface for its networking
2. The loaded DELQA virtual adapter "XQA" is connected to the "packet_port" object "XQA0"

...

Some network adapters available in the CHARON VM are preloaded (for example, the SGEC controller for the MicroVAX 3100 with the predefined name "EZA"), so their configuration is even more simple:

...

After few seconds the chosen interface will be assigned to CHARON:

Follow this link for more details of CHARON VM network controllers configuration.

...

Auto boot

CHARON can be configured to automatically boot an operating system at start up.

The MicroVAX 3100, VAX/PDP11 6310 and VAX/PDP11 4000 models boot automatically if the correct boot flags are set with at the VAX/PDP11 console level:

Please check that the TOY, EEPROM and ROM containers (see above) are enabled so console command changes the updated parameters are saved between rebootsupon reboot.

The ROM of certain VAXes VAX models (MicroVAX II, MicroVAX 3600, MicroVAX 3900, VAXserver 3600 and VAXserver 3900) does not allow the SRM console to accept the commands to enable auto booting. In this case, some parameters a specific parameter can be defined in the configuration file can be used insteadas a workaround:

...

The CHARON-VAX 6000 models have a similar configuration setting:

The CHARON-PDP models have the following setting:

...

These configuration lines are typically specified in the template configuration files ( in commented out form). In case of absence please add the corresponding line according to the examples above.

...

Host load balance for SMP systems

The VAX 6620 through VAX6660 models emulate 2-6 CPUs respectively. In this situation, loading of the host system can be tuned with the following configuration file settings:

...