Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

EXTEND-VM-MEMORY (Increase main memory for a VM)

&pagelevel(4)&pagelevel

/EXTEND-VM-MEMORY enables to enlarge the main memory of a VM, even when the guest system is running. A new value can be set for the minimum main memory size. The reconfiguration of the main memory can be monitored with a monitor job variable.

After the main memory expansion, the new main memory sizes are noted in the VM definition.

The main memory of a VM cannot be enlarged while it is being migrated (VM Migration).

On SU x86, the main memory can be extended to the maximum size set, see "Initializing a VM"and "Reconfiguring main memory".

Main memory reconfiguration is possible for VMs in the INIT-ONLY or DOWN states. In the case of active guest systems (VM state RUNNING), main memory reconfiguration is only possible after SYSTEM READY for the guest system. Main memory reconfiguration is not possible for VMs in state IN HOLD (WAIT).

Since dynamic reconfiguration of main memory requires measures to be taken both in the (active) guest system and in VM2000, the process can be time-consuming. The actual main memory reconfiguration takes place asynchronously after the command has been
accepted. During this time any further /EXTEND-VM-MEMORY or /REDUCE-VM-MEMORY command for the same VM will be rejected.

The /MOVE-VM (SU /390) and /START-VM commands can be executed during main memory reconfiguration. In this case, the new main memory size is used as the main memory size for the relevant VM. The same applies when the guest system is restarted.

On SU x86, aborting a main memory reconfiguration with /START-VM, /RESET-VM or /DELETE-VM should be avoided.
Reason: The reconfiguration will only be aborted in BS2000 but continued in the firmware and the carrier system. A BS2000 IPL with /START-VM may be delayed until the reconfiguration in the carrier system is complete.

This command is reserved for the VM2000 administrator.


EXTEND-VM-MEMORY

VM-IDENTIFICATION = <integer 1..99> / <name 1..8>

,NEW-MEMORY-SIZE = *UNCHANGED / *MAXIMUM /

<integer 1..1048576>(DIMENSION = *MEGABYTE / *GIGABYTE)

,NEW-MIN-MEMORY-SIZE = *UNCHANGED / *MAXIMUM /

<integer 1..1048576>(DIMENSION = *MEGABYTE / *GIGABYTE)

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

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


VM-IDENTIFICATION = <integer 1..99> / <name 1..8>
Identifies the virtual machine by means of a VM index or VM name. The monitor VM’s main memory can also be enlarged.


NEW-MEMORY-SIZE = *UNCHANGED / *MAXIMUM / <integer 1..1048576> (DIMENSION = *MEGABYTE / *GIGABYTE)
New size of main memory after enlargement for the relevant VM up to a size of 1 Tbyte
(terabyte; 1 Tbyte = 1024 Gbytes = 1 048 576 Mbytes).

If *MAXIMUM is specified, the main memory size is increased up to the next VM or to the end of the available main memory.
The value must be a multiple of 2 Mbytes. It may not be greater than the MAX-MEMORY-SIZE of the VM. When *MAXIMUM is specified, the main memory size is extended to the MAX-MEMORY-SIZE of the VM. When the NEW-MEMORY-SIZE of the VM is greater than the main memory which is available, the VM is assigned the main memory which is available.


NEW-MIN-MEMORY-SIZE = *UNCHANGED / *MAXIMUM / <integer 1..1048576> (DIMENSION = *MEGABYTE / *GIGABYTE)
New minimum size of the main memory for the relevant VM when main memory is reconfigured. The new minimum size of the main memory must not be less than the previous minimum size.

The value must be a multiple of 2 Mbytes.

If *MAXIMUM is specified, the main memory size defined by (NEW-)MEMORY-SIZE is chosen for the VM.


MONJV =
Defines a MONJV for monitoring the reconfiguration of the main memory (see the corresponding paragraph in section "Reconfiguring main memory").

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
1             0
64
64
64
64
64

64
64
64
128

CMD0001
CMD0001
VMS2070
VMS4000
VMS4011
VMS4071
VMS4091

VMS4092
VMS4093
VMS4340
VMS3042

Command successfully executed
No action required
VM in the IN HOLD (WAIT) state
VM not yet created
Requested memory size or location not available
Invalid memory size or location
A guest system for which main memory reconfiguration
is not possible is running on the VM
Memory reconfiguration is still active
Invalid memory size
Opening of MONJV rejected by subsystem JV
VM being migrated


Guaranteed messages

VMS2306 (SU /390)


Example

/show-vm-resources information=*memory ————————————————————————————————  (1)
VM-ID        LOC-BEGIN  MEM-SIZE  MIN-MEM-S  MAX-MEM-S  DEST-MEM-S
HYPERVISOR   00000000         16

 1 MONITOR   00000010        512        512
 2 SYSTEM2   00000210        512        512
NONE         00000410      14832
LARGEST FREE DOMAIN:       14832
/extend-vm-memory vm-id=2,new-memory-size=768 —————————————————————————  (2)
/show-vm-resources information=*memory
VMS4094 MEMORY-RECONFIGURATION FOR VIRTUAL MACHINE (2,SYSTEM2) HAS BEEN

        SUCCESSFULLY PROCESSED. CURRENT MEMORY SIZES: 512 / 768 ———————  (3)
VM-ID        LOC-BEGIN  MEM-SIZE  MIN-MEM-S  MAX-MEM-S  DEST-MEM-S
HYPERVISOR   00000000         16
 1 MONITOR   00000010        512        512
 2 SYSTEM2   00000210        768        512 ———————————————————————————  (4)
NONE         00000510      14576
LARGEST FREE DOMAIN:       14576

------------------------------------------------------------------------------------------------------------------

(1)

The VM2000 administrator fetches information on the main memory distribution in VM2000. VM2 has a main memory size of 512 Mbytes and a minimum memory size of 512 Mbytes. Since the guest system on VM2 has already reached SYSTEM READY it is possible to reconfigure the main memory in this guest system. The subsequent memory area has not been assigned, so that the main memory for VM2 can be enlarged.

(2)

The main memory for VM2 is to be enlarged to 768 Mbytes. The minimum main memory size is unchanged.

(3)

After its completion, the result of the asynchronously executing reconfiguration request is reported to the VM2000 administrator as an asynchronous (guaranteed) message in the user event stream or displayed at the next input (main memory reconfiguration is time-consuming).

(4)

The main memory size for VM2 is now 768 Mbytes. This reduces the remaining free main memory.