VM2000 in the guest systems

VM2000 in the monitor system and the other BS2000 guest systems

This section is also aimed at systems support in all BS2000 guest systems (even in the monitor system). It describes how (guest) systems support receives information on VM2000 and how it can use VM2000 functions for the guest system. In addition, the VM2000 functions are mentioned whose execution entails the interworking of VM2000 and the guest system.

A guest system in VM2000 is partitioned off from the other guest systems. It behaves in production operation like an operating system in native operation.

The following options for information output and interaction are offered for a guest system (thus also for the monitor system):

For all Server Units

• The nonprivileged macro VMGINF provides global VM2000 information (see the “Executive Macros” manual [16]).

• Output of global VM2000 information in all guest systems (see "SHOW-SYSTEM-INFORMATION (Display information on the current system)" and the BS2000 command /SHOW-SYSTEM-INFORMATION in the “Commands” manual [13]).

• Output of VM2000 information on devices and pubsets in the guest system as well (see "SHOW-DEVICE-CONFIGURATION (Display system configuration and availability)" and the BS2000 command /SHOW-DEVICE-CONFIGURATION in the “Commands” manual [13]).

• In the case of /SHUTDOWN-VM, VM2000 and the guest systems concerned interwork to execute shutdown processing (see "Terminating the monitor system and VM2000").

• Dynamic main memory reconfiguration is carried out by VM2000 together with the guest system (see "Reconfiguring main memory").

• Implicit assignment of (pubset) devices to the VM and implicit release of (pubset) devices of the VM by the operator in the guest system (see "Assignment sets, implicit device assignment and release" and the description of the BS2000 reconfiguration commands mentioned there as of "ATTACH-DEVICE (Attach hardware units)" and in the “Commands” manual [13]).

• For devices that are attached in the guest system and that are possibly still in use, explicit device assignment can be converted to an implicit device assignment. The device then remains with the VM until the guest system detaches the device (see section "Explicit device assignment and removal").

• The BS2000 utility routine IORM can be used in all guest systems. It operates on a cross-guest-system basis and is administered in the monitor system. The I/O limit of the IORM function IOLVM is set on SU /390 by means of VM2000 commands (see "Use of IORM in VM2000 operation" and the “Utility Routines” manual [3]).

• In the case of measurements with the openSM2 measurement monitor, measurement information on the VM of the guest system is output in the VM2000 report and in the SM2R1 reports 98 and 99 (see "Measurement with the openSM2 measurement monitor" and the “openSM2” manual [9]).

• The guest systems are informed about the failure of the monitor system and about the renewed readiness of the system for operation (messages NRTV001 - NRTV003, see "Automatic restart after SETS in the monitor system").

• Guest systems are included in certain steps of the VM Migration.

For SU /390

• In the case of /MOVE-VM, VM2000 and the guest systems concerned interwork to provide protection in the MSCF network (see "Moving a VM within main memory").

• Using BS2000 command /MODIFY-IO-UNIT you can specify in a guest system a different base or alias device that is to be preferred for I/Os of this guest system (see "Parallel access volume (PAV, SU /390)" and the command description in the “Commands” manual [13]).

• Using BS2000 command /MODIFY-IO-OPTIONS you can specify in a guest system whether base or alias devices of feature "FastDPAV" are to be preferred for I/Os of this guest system (see "Parallel access volume (PAV, SU /390)" and the command description in the “Commands” manual [13]).

• SLEDFILES with the dump object VM2000 can be evaluated with DAMP (see "Analyzing SLEDFILEs with DAMP" and the “Diagnostics Handbook” manual [4]).

• In the case of guest system SLEDs, the diagnostic data of the VM2000 hypervisor is contained in the SLEDFILE (see "Guest system errors" and the “Introduction to System Administration” manual [2]).

VM2000 in the monitor system

The monitor system has a special role.

The following options for information output and controlling the guest system operation are additionally offered for the monitor system:

For all Server Units

• The security administrator in a BS2000 guest system can use the VIRTUAL-MACHINE-ADMINISTRATION and VM2000-ADMINISTRATION privileges to permit the operation of his/her own VM or of VM2000 for a user task using VM2000 commands (see "Operating the virtual machines (ADMIN dialog from user task)" and the “Introduction to System Administration” [2]).

• In measurements using the openSM2 measurement monitor, measurement information on all VMs is output in the VM2000 report and in SM2R1 reports 98 and 99 (see "Measurement with the openSM2 measurement monitor" and the “openSM2” manual [9]).

• Using BS2000 command /MODIFY-IO-OPTIONS you can specify a new timeout value for the specified devices by the operating in the monitor system centrally for all guest systems (see also the command description in the “Commands” manual [13]).

For SU /390

• (Global) reconfiguration of hardware units and paths in all the active guest systems by the operator in the monitor system (see "Reconfiguring Channels, controllers and paths (SU /390)" and the description of the BS2000 reconfiguration commands mentioned there as of "ATTACH-DEVICE (Attach hardware units)" and in the “Commands” manual [13]).

• Interaction between VM2000 and the operating in the monitor system during dynamic I/O configuration modification of channel devices (see "Changing the configuration of channel devices using BS2000 (SU /390)" and the “Introduction to System Administration” manual [2]).