ACTIVATE-VM-DEFINITION (Activate a VM definition)

/ACTIVATE-VM-DEFINITION activates a VM definition, i.e. a VM is initialized with the attributes entered in the VM definition. The devices entered in the VM definition are assigned to the VM. If required, the guest system on the VM is started in accordance with the settings for automatic startup in the VM definition. The VM definition may not belong to a VM which has already been initialized.

The VM can be monitored with a monitor job variable.

This command is reserved for the VM2000 administrator.

ACTIVATE-VM-DEFINITION

VM-NAME = <name 1..8>

,MONJV= *NONE / <filename 1..54 without-gen-vers>

,JV-PASSWORD = *NONE / <c-string 1..4> / <x-string 1..8> / <integer -2147483647..2147483648>

VM-NAME = <name 1..8>
Name of the VM definition.
Identical to the name of the virtual machine which is to be initialized.

MONJV =
Defines a MONJV for monitoring the VM (see "Monitoring a VM with job variables (MONJV)").

MONJV = *NONE
No MONJV is defined.

MONJV = <filename 1..54 without-gen-vers>
The specified MONJV is supplied with data by VM2000; therefore, the sender of the command must have write permission for the specified MONJV.
If no catalog ID or user ID is specified in the file name, VM2000 completes the file name, in accordance with the runtime environment of the sender of the command.
If the specified file name does not refer to an existing job variable, VM2000 creates the MONJV as shareable and without a password.

JV-PASSWORD = *NONE / <c-string 1..4> / <x-string 1..8> / <integer ...>
Password of the MONJV for checking access authorization.
The input field is automatically blanked in the guided dialog. The value input is not logged.

This operand is only evaluated if a previously created job variable was specified with MONJV.

 

Command return codes

(SC2)   SC1	Main code	Meaning
0 2             0 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64	CMD0001 VMS2306 VMS2101 VMS2300 VMS2303 VMS2314 VMS2316 VMS2318 VMS2332 VMS3035 VMS4004 VMS4006 VMS4010 VMS4011 VMS4014 VMS4015 VMS4016 VMS4032 VMS4033 VMS4034 VMS4064 VMS4067 VMS4089 VMS4170 VMS4200 VMS4250 VMS4251 VMS4252 VMS4340 VMS4400 VMS4513 VMS4600 VMS4612	Command successfully executed VM definition could not be updated (last IPL parameter in a definition with AUTO-IPL=*YES) VM2000 shutdown in progress VM definition does not exist VM definition cannot be accessed Conflict in the device usage mode between the pubset and the PUBRES device VM index greater than the current maximum number of VMs VM index is already used by an initialized VM Storage for VM definitions cannot be reached (SU /390) IO-PRIORITY cannot be set (total of virtual CPUs with privilege too high) Device already assigned to a VM Device not available (not defined) Maximum permitted number of VMs already reached Requested memory size or location not available SVP error VM already initialized Device cannot be used as a virtual console Device cannot be assigned to several VMs at the same time Maximum number of sharers already reached Device is currently in shared use No channel path available Resource bottleneck in the hardware Virtual console must be assigned with TYPE=*VC I/O execution mode cannot be set to “indirect“ Assignment set not yet created Device is not a PUBRES device Device list of the pubset is inconsistent Device list for PUBRES cannot be determined MONJV could not be accessed VM group not yet created Hypervisor memory bottleneck CPU pool not yet created No attached CPU in the CPU pool

Guaranteed messages

VMS4005

Only on SU /390:  VMS3050, VMS4425, VMS4615

Only on SU x86:  VMS6020

Example

See section "Examples of working with VM definitions".