Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Setting up the VM2000 monitor

&pagelevel(3)&pagelevel

The VM2000 monitor is designed as a separate DSSM subsystem VM2-MON with its own parameter file. It executes in the monitor system and implements the administration interface for VM2000 operation.

VM2000 is thus independent of the generation of BS2000.

The monitor REP file must be self-contained; it must not be incorporated in the BS2000 REP loader.


The VM2-MON subsystem has the following properties:

  • It is independent of the operating system version in the monitor system

  • It is loaded automatically by DSSM before SYSTEM READY

  • It can process VM2000 commands from the CMDFILE

  • It is active during the entire system run

  • It cannot be controlled by DSSM commands

  • It cannot be replaced while the system is running


The VM2000 monitor uses the functions available in BS2000, e.g.:

  • Administration from a privileged user task

  • Processing command input via SDF and passing it to the processing routines, which then convert these commands into hypervisor calls

  • Executing message output, guaranteed messages

  • SHOW output in structured S variables

  • Accounting tasks for VM2000 and virtual machines.


The central VM2000 monitor functions are implemented by the following system tasks:

VM2M
VM2G
VM2J
VM2C
VM2P
VM2E
VM2T

Main task, command processing
General task, executing or distributing jobs (SU /390)
Job variable task, updating the MONJVs of VM2000
VMCONS task, execution of $VMCONS
Pubset task, determining the pubset devices
Task for processing requests of the VM2000 Agent (SU x86)
Task for processing requests of an MU or for a VM Migration on the target SU (SU /390)

 

Parameter file for the VM2-MON subsystem

The parameters of the VM2-MON subsystem are determined in the parameter file SYSPAR.VM2000-MON.<ver>.SSP. The following parameters can be entered:

VMCONS-OPERID = VMADMIN / <name 1..8>

Operator ID of $VMCONS (user ID, see "Preparing to use $VMCONS") for establishing a connection to $CONSOLE.

VMCONS-OPERID-PASSWORD = *NONE / <c-string 1..8>

Password for the $VMCONS operator ID. Hexadecimal passwords are not permitted.

VMCONS-OPERATOR-ROLE = VM2000 / <name 1..8>

Operator role for $VMCONS (see "Preparing to use $VMCONS").

VMCONS-PASSWORD = *NONE / <c-string 1..4> / <x-string 1..8>

Password for establishing a connection to $VMCONS. A password comprising only zeros (X'00...00') is ignored (the effect is the same as with *NONE).

 The following parameter is only relevant on SU /390:

LM-TASK-PRIORITY = *HIGH / <integer 60..255>

Specification of the priority for the VM2000 system tasks that control and perform a VM Migration in the monitor systems of the affected Server Units (source and target SU). The highest possible priority is the default value (*HIGH, corresponds to the value 60).If the priority of the VM2000 system tasks for controlling and performing VM Migrations is reduced, i.e. the value for LM-TASK-PRIORITY is increased, other tasks in the monitor system have a higher probability of being allocated CPU capacity. This can be especially important for a monitor system with the MONO multiprocessor level.

The operand names and keywords must not be abbreviated. If no specification is made or if the specifications are incorrect, the defaults (underscored) are used. If parameters are specified more than once, the most recently specified value applies. Comment lines are introduced by an asterisk (*).

 

Coexistence of different VM2000 versions on BS2000

The VM2000 parameter VERSION (in SYSPAR.BS2.<ver>) controls the VM2000 version to be selected. The default setting for the monitor system BS2000 V21.0 is VERSION=V12.0.

See section "Setting the VM2000 parameters in the parameter service".

Note on the coexistence of multiple VM2000 versions

If multiple versions of the subsystem VM2-MON are installed with IMON, the following must be taken into account:

  • An entry for the version-specific message file is contained in the MIP parameter file for each installed version of VM2-MON. When the monitor system is started, the message files of all installed versions of VM2-MON are activated. In a current session, the message file which belongs to the started version of subsystem VM2-MON is used. If you want to prevent the superfluos message files from being activated, you can remove them from the MIP parameter file using /MODIFY-MIP-PARAMETERS.  If required, removed entries can be added using /MODIFY-MIP-PARAMETERS again.

  • An entry for the version-specific SDF syntax file is contained in the SDF parameter file for the version of VM2-MON installed most recently. When the monitor system is started, only this SDF syntax file is activated. If it is not the desired version of the SDF syntax file of VM2-MON, you can correct the entry in the SDF parameter file using /MODIFY-SDF-PARAMETERS.

The parameter files need not be cleared for VM2000 operation normally, mainly not in case you want to start the version of VM2-MON installed most recently.