The LM can be controlled also with VM2000 administrator commands in VM2000 operation mode.
The command is entered in the monitor system of the source SU and in contrast to operation through SE Manager the name of the target SU must be entered explicitly here.
For SU /390 the SU name is the same as the BCAM hostname of the monitor system, for SU 86 the SU name is the X2000 host name.
(Note regarding SU /390: In SEM the names of the SU /390 are freely configurable. These names are used in all SEM displays and actions.)
In the following, the commands /MIGRATE-VM, /CHECK-VM-MIGRATION and /MIGRATE-VM-DEFINITION are explained.
These commands are described in detail in the VM2000 user manual [3].
Command /MIGRATE-VM
/MIGRATE-VM initiates the Live Migration.
The system that needs to be migrated is specified through the VM index or VM name.
Example of an LM of the guest system with VM index 12 for the target SU ABGSE701:
/MIGRATE-VM VM-ID=12,SERVER-UNIT-NAME=ABGSE701
The progress of the LM is protocolled on the console with messages.
Additionally, the progress can also be monitored with a MONJV.
Example of an LM with specification of the VM name of the guest system that needs to be migrated and of a MONJV to monitor the LM, for example from an SDF-P procedure:
/MIGRATE-VM VM-ID=VM12PROD,SERVER-UNIT-NAME=ABGSE701,MONJV=MONJV.LM.VM12PROD
After sending the command the status of the LM is displayed in one of the first three bytes of the MONJV. Further information follows it (see current handbook for VM2000).
Possible values of the status of the MONJV and their meanings are:
| Status | Meaning |
|---|---|
$S | Task accepted for migration |
$R | Migration in progress |
$T | Migration terminated normally |
$TW | Migration terminated with warnings |
$AE | Migration ended abnormally because of errors |
$AF | Migration task rejected |
The command checks the preconditions for carrying out an LM.
Checking serves the purpose of finding possible issues in the configuration in the preliminary stages of a planned LM.
The command /MIGRATE-VM also executes the function /CHECK-VM-MIGRATION (first) internally.
The result of the check is returned through VM2000 messages.
Example:
/CHECK-VM-MIGRATION VM-ID=12,SERVER-UNIT-NAME=ABGSE501
% VMS2404 LIVE MIGRATION OF VM (12,VM12PROD) REJECTED BY THE TARGET SU 'ABGSE501'. REASON:
VMS2437,4683
% VMS2461 LIVE MIGRATION OF VM (12,VM12PROD) TO TARGET SU 'ABGSE501' NOT POSSIBLE
/HELP-MSG-INFORMATION MSG-IDENTIFICATION=VMS2437,LANGUAGE=E
% VMS2437 DEVICE '(&00)' NOT ASSIGNABLE TO VIRTUAL MACHINE ON THE TARGET SU
% ? (&00): Mnemonic device name
% The device is already assigned (exclusively) to another VM.
LM cannot be done in this situation, because the system to be migrated is using a device with MN 4683 on the source SU, but on the target SU this device is assigned exclusively to a different VM.
As measure the device must either be made available on the target SU or removed from the system to be migrated on the source SU.
After removing the inconsistency, the command delivers a positive result:
/CHECK-VM-MIGRATION VM-ID=12,SERVER-UNIT-NAME=ABGSE501
% VMS2460 LIVE MIGRATION OF VM (12,VM12PROD) TO TARGET SU 'ABGSE501' POSSIBLE
The LM is now possible.
Command /MIGRATE-VM-DEFINITION
Persistent VM definitions of not initialized VMs (state DEFINED_ONLY in SE Manager) are transferred with this VM2000 administration command within an SU Cluster from the local SU of the cluster that needs to be removed.
In the VM2000 monitor system one receives the message DEFINED_ONLY as status ACT[IVE]=NO:
/SHOW-VM-DEFINITION
% CPU-POOL(P)
% VM-ID ACT PER HA VM-GROUP(G) PROC MEM-SIZE MAX-IO
...
% - OSD11TST NO YES NO *STDPOOL(P) 1 512 100
...
% 12 VM12PROD YES YES NO *STDPOOL(P) 1 2048 100
The VM with the VM name OSD11TST isn’t active (ACT = NO), which means that its VM definition can be transferred with the command /MIGRATE-VM-DEFINITION to the SU ABGSE501:
/MIGRATE-VM-DEFINITION VM-NAME=OSD11TST,SERVER-UNIT-NAME=ABGSE501
% VMS2320 DEFINITION OF VM 'OSD11TST' MIGRATED TO TARGET SU 'ABGSE501'
The VM with the VM name VM12PROD is active (ACT = YES), which means that its VM definition cannot be transferred with the command /MIGRATE-VM-DEFINITION:
/MIGRATE-VM-DEFINITION VM-NAME=VM12PROD,SERVER-UNIT-NAME=ABGSE501
% VMS4015 VIRTUAL MACHINE (12,VM12PROD) ALREADY INITIALIZED. /MIGRATE-VM-DEFINITION REJECTED