Monitoring a VM Migration with job variables (MONJV)

When the VM Migration is initialized by the VM2000 administrator with /MIGRATE-VM, a monitoring job variable (MONJV) can be defined.
The location and validity of the MONJV correspond to the runtime environment of the sender of the command. VM2000 manages and updates the MONJV while the VM Migration is running. By using appropriate procedures, the VM2000 administration can automatically react to the information stored in the MONJV and thus facilitate VM2000 administration.

For general information on job variables in VM2000, see "Monitoring a VM with job variables (MONJV)".

MONJVs can also be used to monitor a VM and for main memory reconfiguration, see "Monitoring a VM with job variables (MONJV)" and "Reconfiguring main memory". You can find examples for using MONJV in these sections.

Beginning and end of monitoring

The MONJV used to monitor the VM Migration is configured when the VM Migration is initialized with /MIGRATE-VM by specifying the operand MONJV. The monitoring of the VM Migration begins at this point; the MONJV is supplied with data by VM2000.

If a MONJV already exists with the specified name and with a password, this password can be specified in the operand JV-PASSWORD to check for access authorization.

As soon as the VM Migration is regularly or irregularly terminated, the monitoring is stopped as well. Even when the monitoring has finished, the MONJV is retained as a user job variable without MONJV protection.

Protecting the MONJV

See the paragraph with this name in the section "Monitoring a VM with job variables (MONJV)".

Location of the MONJV

See the paragraph with this name in the section "Monitoring a VM with job variables (MONJV)".

 

Values for the MONJV

A MONJV for a VM Migration comprises a system part (bytes 1-128) and a user part (bytes 129-256).
Specific values are entered by VM2000 in the system part of the MONJV at specific times during the execution of the VM Migration.

Byte	Meaning / possible values
1-3	Monitoring status (left-aligned, padded with a space): $S  : VM Migration initiated $R  : VM Migration running $T  : VM Migration successfully terminated $TW : VM Migration terminated with warnings $AE : VM Migration aborted due to error $AF : VM Migration rejected
4	Reserved, has the value zero (0)
5-8	Reserved, contains spaces
9-12	Catalog ID of the home pubset of the monitor system (left-aligned, padded with spaces)
13-16	Reserved, contains spaces
17	Type of MONJV: character V (VM2000)
18-20	Current system sequence number (<integer 1..999>)
21-36	Beginning of monitoring (opening the MONJV) in UTC time (format: yyyy-mm-ddhhmmss)
37-70	Reserved
71-78	Name of the VM (<name 1..8>)
79	Reserved, has the value zero (0)
80-81	Index of VM printable (<name 2..2>, e.g. 02)
82-89	Name of the target SU (<composed_name 1..8>, possibly shortened)
90-128	Only for $TW and $AE states: supplementary information For $TW:                VM could not be deleted For $AE: Aborted after restart of monitor Monitor memory shortage Connection to target SU disturbed Continuation rejected by guest system Continuation by guest system in delay Detach of device <mn> rejected Detach of device <mn> in delay Device <mn> busy Internal error Aborted by VM2000 on target SU Error recovery or reconfig in progress Aborted by VM system VM deleted regardless to its state Too many changing memory pages Hypervisor memory exhausted
129-256	Reserved for users

Displaying the MONJV

See the paragraph with this name in the section "Monitoring a VM with job variables (MONJV)".

The name of the MONJV is displayed in the VM2000 commands /SHOW-VM-ATTRIBUTES and /SHOW-VM-RESOURCES using the operand INFORMATION=*MONJV/*ALL as MIGR-MONJV.

Behavior when the system is terminated abnormally in the monitor system

See the paragraph with this name in the section "Monitoring a VM with job variables (MONJV)".