Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

MODIFY-VM-ATTRIBUTES (Modify attributes of a VM)

&pagelevel(4)&pagelevel

/MODIFY-VM-ATTRIBUTES is used to modify the attributes of an initialized VM.

The modified attributes and specifications are noted in the VM definition.

The following attributes can be modified:

  • The CPU quota

  • Maximum CPU utilization of the VM

  • Maximum I/O utilization of the VM (SU /390)

  • Password for administration

  • Command range for VM2000 administrator and VM administrator

  • The privileges for the VM

  • Settings for controlling the real CPU (SU /390)

  • The scope of the trace entries for VM2000 to be logged

  • The PERSISTENT attribute

  • The information for automatically starting the guest system on a persistent VM when next activating its VM definition

The attributes of a VM cannot be changed while it is being migrated (VM Migration).

You can modify the attributes and resources entered in the VM definition of a VM which has not yet been initialized using /MODIFY-VM-DEFINITION.

This command is reserved for the VM2000 administrator and VM administrators with ADMIN-PRIVILEGES=*MAXIMUM.


MODIFY-VM-ATTRIBUTES

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

,CPU-QUOTA = *UNCHANGED / <fixed 0.01..99.99> / *BY-VM-GROUP(...)


*BY-VM-GROUP(...)



|

MEMBER-CPU-QUOTA = *UNCHANGED / <fixed 0.01..99.99>

,MAX-CPU-UTILIZATION = *UNCHANGED / <fixed 0.01..100.00>

,MAX-IO-UTILIZATION = *UNCHANGED / <integer 1..100>

,PASSWORD =*UNCHANGED / *NONE / <c-string 1..8> / <x-string 1..16>

,ADMIN-PRIVILEGES = *UNCHANGED / *STD / *MINIMUM / *MAXIMUM

,PRIVILEGES = *PARAMETERS(...)


*PARAMETERS(...)



|

IO-RESET = *UNCHANGED / *NO / *YES



|

,IO-PRIORITY = *UNCHANGED / *NO / *YES



|

,AUTO-SNAP-ASSIGNMENT =*UNCHANGED / *NO / *YES



|

,ASSIGN-BY-GUEST = *UNCHANGED / *NO / *YES(...)



|


*YES(...)



|



|

SET-NAME = *STDSET / *ALL / *EXCEPT(...) / *ADD(...) / *REMOVE(...) /



|



|





list-poss(8): <name 1..8> / *STDSET



|



|


*EXCEPT(...)



|



|



|

SET-NAME = list-poss(8): <name 1..8> / *STDSET



|



|


*ADD(...)



|



|



|

SET-NAME = list-poss(8): <name 1..8> / *STDSET



|



|


*REMOVE(...)



|



|



|

SET-NAME = list-poss(8): <name 1..8> / *STDSET

,VM-ACTIVE-IDLE= *UNCHANGED / *NO / *AT-DEDICATED-CPUS

,TRACE-LEVEL = *UNCHANGED / *OFF / *STD / *MAXIMUM

,VM-NAME = *UNCHANGED / <name 1..8>

,PERSISTENT = *UNCHANGED / *NO / *YES(...)


*YES(...)



|

,AUTO-IPL= *NO / *YES(...)



|


*YES(...)



|



|

IPL-UNIT = *UNCHANGED-OR-NONE / <alphanum-name 2..2> / <x-text 4..4>



|



|

,IPL-CONSOLE = *UNCHANGED-OR-NONE / <alphanum-name 2..2>



|



|

,MODE = *UNCHANGED-OR-AUTOMATIC / *AUTOMATIC / *FAST



|



|

,SYSTEM-NAME = *UNCHANGED-OR-NONE / *NONE / <name 1..8>


If no more detailed explanation is specified, the operand value *UNCHANGED means that the existing setting for the operand value is retained.


VM-IDENTIFICATION = <integer 1..99> / <name 1..8>
Identifies the virtual machine by means of a VM index or VM name.


CPU-QUOTA =
This determines whether the CPU quota is to be changed or retained.

CPU-QUOTA = <fixed 0.01..99.99>
New CPU quota for a VM which does not belong to a VM group, see "Planning distribution of the CPU capacity to the VMs".

CPU-QUOTA = *BY-VM-GROUP(...)
New member CPU quota for a VM which belongs to a VM group (SU /390), see "Operating VM groups (SU /390)".

MEMBER-CPU-QUOTA =
Defines whether the member CPU quota is to be modified or retained.

MEMBER-CPU-QUOTA = *UNCHANGED
The previous member CPU quota is retained.

MEMBER-CPU-QUOTA = <fixed 0.01..99.99>
New member CPU quota.


MAX-CPU-UTILIZATION =
Determines whether the maximum CPU utilization of the VM is to be changed or retained.

MAX-CPU-UTILIZATION = <fixed 0.01..100.00>
New maximum CPU utilization of the VM, see "Planning distribution of the CPU capacity to the VMs".

If the VM belongs to a VM group (SU /390), its maximum CPU utilization is also restricted by the “maximum CPU utilization of the VM group” (see "Operating VM groups (SU /390)").

   

MAX-IO-UTILIZATION =
On SU /390, determines whether the maximum I/O utilization of the VM is to be changed or retained.

MAX-IO-UTILIZATION = <integer 1..100>
New maximum I/O utilization of the VM, see "Use of IORM in VM2000 operation".


PASSWORD =
This determines whether the password which determines the right of access in /BEGIN-VM-DIALOG is to be changed or retained. The password can be up to 8 bytes long.

PASSWORD = *NONE
No password is to be defined.

PASSWORD = <c-string 1..8>
New password in character form.

PASSWORD = <x-string 1..16>
New password in hexadecimal form.


ADMIN-PRIVILEGES =
Determines whether the command/function range for VM2000 and VM administrators is to be changed or retained (see "Extending and restricting the range of commands/functions").

ADMIN-PRIVILEGES = *STD
Standard command/function range for the VM administrator.

ADMIN-PRIVILEGES = *MINIMUM
Restricted command/function range for the VM2000 administrator.

For security reasons, a command/function range restricted by means of *MINIMUM cannot be revoked during the session.

ADMIN-PRIVILEGES = *MAXIMUM
Extended command/function range for the VM administrator. This operand value may not be specified for the monitor VM.


PRIVILEGES = *PARAMETERS(...)
Describes privileges of the VM (see "Initializing a VM").
If *UNCHANGED is specified, the privileges of the VM remain unchanged.

IO-RESET = *NO / *YES
Specifies on SU /390 whether the channels are reset in the hardware for this VM at /START-VM or when the guest system is restarted or the channels reconfigured.

IO-PRIORITY = *NO / *YES
Specifies on SU /390 whether a waiting virtual CPU of the VM is executed again on a real CPU by the VM2000 hypervisor immediately after the end of pending input/output for this VM.

The total number of virtual CPUs of all the VMs with this privilege may not be greater than the number of the real normal CPUs of the Server Unit.

AUTO-SNAP-ASSIGNMENT = *YES / *NO
Determines whether the guest system of the VM may assign snap units for Snapsets implicitly without the VM and devices being assigned the ASSIGN-BY-GUEST privilege or attribute.

ASSIGN-BY-GUEST = *NO / *YES(...)
Specifies whether devices can also be assigned implicitly to this VM by the guest system (*YES).
Alternatively (*NO), the devices must be assigned explicitly to the VM by the VM or VM2000 administrator.

SET-NAME =
Determines the assignment sets from which the guest system may assign devices implicitly to the VM. A VM can be assigned up to 28 assignment sets by means of explicit list specification.

SET-NAME = *STDSET / list-poss (8): <name 1..8> / *STDSET
Explicit specification of the assignment sets.

SET-NAME = *ALL
All existing and future assignment sets.

SET-NAME = *EXCEPT(SET-NAME = list-poss (8): <name 1..8> / *STDSET)
All existing and future assignment sets with the exception of those which are specified with SET-NAME.

SET-NAME = *ADD(SET-NAME = list-poss (8): <name 1..8> / *STDSET)
Extends the existing set of assignment sets for the VM.

SET-NAME = *REMOVE(SET-NAME = list-poss (8): <name 1..8> / *STDSET)
Reduces the existing set of assignment sets for the VM.


VM-ACTIVE-IDLE =
Determines on SU /390 whether, in the event of fixed CPU assignment (dedicated CPUs), a VM still retains control over the real CPU if the VM’s virtual CPU which runs on this is inactive (interruptible wait state, "Idle"), see "Initializing a VM".

VM-ACTIVE-IDLE = *NO
The VM leaves control over the real CPU if the VM’s virtual CPU which runs on this becomes inactive (interruptible wait state).

VM-ACTIVE-IDLE = *AT-DEDICATED-CPUS
The VM retains control over the real CPU even if the VM’s virtual CPU which runs on this is inactive (interruptible wait state, "Idle").
This idle time is then indicated in the VM2000 accounting records, with /SHOW-VM-STATUS (VM-ACTIVE output column) and in the VM2000 report of openSM2 as a time in which the VM actively uses the real CPU.

With fixed CPU assignment, VM-ACTIVE-IDLE=*AT-DEDICATED-CPUS is only effective if the VM’s maximum CPU utilization (see "Initializing a VM") is not restricted.


TRACE-LEVEL =
Specifies the scope of the trace entries for VM2000 to be logged (see "Other diagnostic aids"). This operand can only be specified for the monitor VM.
The default value after starting the monitor system is *OFF.

TRACE-LEVEL = *OFF
Only entries in the error trace are logged (system errors).

TRACE-LEVEL = *STD
Entries in the error trace and the important points of the runtime trace and the $VMCONS trace are logged.

TRACE-LEVEL = *MAXIMUM
All trace entries are logged.


VM-NAME =
Determines whether accounting records are to be written.

VM-NAME = <name 1..8>
The name of a VM can no longer be changed. The old name must be specified. The entry VM-NAME=<old name> causes the accounting records to be written (see "Accounting in VM2000").


PERSISTENT =
Determines whether the PERSISTENT attribute is assigned to or removed from the VM which has already been initialized.
For a VM which is already persistent, the setting can be modified whether the guest system on the VM is to be started automatically the next time the VM definition is activated (AUTO-IPL operand). When the guest system on the VM which is already persistent is to be started automatically the next time the VM definition is activated, the specifications for the automatic startup of the guest system on the VM can be modified.
This operand cannot be specified for the monitor VM.

PERSISTENT = *NO
The PERSISTENT attribute is removed from a persistent VM. This is also entered in the VM definition. Specifications entered earlier for the IPL-UNIT, IPL-CONSOLE, MODE and SYSTEM-NAME parameters are deleted in the VM definition. The VM definition is no longer persistent.

PERSISTENT = *YES(...)
The VM is assigned or retains the PERSISTENT attribute. This is also entered in the VM definition. The VM definition becomes or remains persistent.

AUTO-IPL =
Determines whether the guest system on the VM is to be started automatically when the VM definition is activated.

AUTO-IPL = *NO
The guest system on the VM is not started automatically.

The IPL-UNIT, IPL-CONSOLE, MODE and SYSTEM-NAME parameters set for a persistent VM are retained in the VM definition and can be reactivated using this command and the specification AUTO-IPL=*YES.

AUTO-IPL = *YES(...)
The guest system on the VM is started automatically.
The parameters for the automatic startup must be supplied with values appropriately.

IPL-UNIT = *UNCHANGED-OR-NONE
When a non-persistent VM is assigned the VM attribute PERSISTENT, IPL-UNIT=*NONE is entered in the VM definition. In the case of a VM which is already persistent (e.g. when switching from AUTO-IPL=*NO to AUTO-IPL=*YES), the existing entry for IPL-UNIT in the VM definition is retained.

IPL-UNIT = <alphanum-name 2..2> / <x-text 4..4>
Mnemonic device name of the disk device used for the initial program loading (IPL) of the guest system. The device must be assigned to the VM explicitly and exclusively.

IPL-CONSOLE = *UNCHANGED-OR-NONE
When a non-persistent VM is assigned the VM attribute PERSISTENT, IPL-CONSOLE=*NONE is entered in the VM definition. In the case of a VM which is already persistent (e.g. when switching from AUTO-IPL=*NO to AUTO-IPL=*YES), the existing entry for IPL-CONSOLE in the VM definition is retained.

IPL-CONSOLE = <alphanum-name 2..2>
Mnemonic device name of the KVP output device.

MODE = *UNCHANGED-OR-AUTOMATIC
When a non-persistent VM is assigned the VM attribute PERSISTENT,
MODE=*AUTOMATIC is entered in the VM definition. In the case of a VM which is already persistent (e.g. when switching from AUTO-IPL=*NO to AUTO-IPL=*YES), the existing entry for MODE in the VM definition is retained.

MODE = *AUTOMATIC / *FAST
Defines the type of system initialization (AUTOMATIC or FAST startup).

SYSTEM-NAME = *UNCHANGED-OR-NONE
When a non-persistent VM is assigned the VM attribute PERSISTENT, SYSTEM-NAME=*NONE is entered in the VM definition. In the case of a VM which is already persistent (e.g. when switching from AUTO-IPL=*NO to AUTO-IPL=*YES), the existing entry for SYSTEM-NAME in the VM definition is retained.
 The specification is ignored on SU /390.

SYSTEM-NAME = *NONE / <name 1..8>
Specifies the system name.
 The specification is ignored on SU /390.


Command return codes

(SC2)   SC1

Main code

Meaning                                          

0
2             0
2             0
64
64
64
64
64

64
64
64
64
64
64
128

CMD0001
CMD0001
VMS2306
VMS2332
VMS3002
VMS3033
VMS3034
VMS3035

VMS3038
VMS4000
VMS4200
VMS4211
VMS4428
VMS4450
VMS3042

Command successfully executed
Decimal specifications rounded to 2 decimal places
VM definition could not be updated (SU /390)
Storage for VM definitions cannot be reached (SU /390)
Invalid operand value
ADMIN-PRIVILEGES=*MAX not permissible for monitor VM
ADMIN-PRIVILEGES=*MIN only permissible for monitor VM
IO-PRIORITY cannot be set
(total of virtual CPUs with privilege too high)
PERSISTENT=*YES not permitted for the monitor VM
VM not yet created
Assignment set not yet created
Maximum number of assignment sets already assigned to the VM
VM does not belong to a VM group
CPU quota must be specified via MEMBER-CPU-QUOTA
VM being migrated


Example

/modify-vm-attributes vm-id=system2,cpu-quota=20,max-cpu-utilization=25,
  privileges=*parameters(assign-by-guest=*yes(set-name=*stdset)) ——————  (1)
/show-vm-attributes vm-id=system2,information=*std ————————————————————  (2)
             CPU-POOL(P)
VM-ID        VM-GROUP(G)  CPU-Q   MAX-U  PROC   MEM-SIZE  MAX-IO
 2 SYSTEM2   *STDPOOL(P)  20.00   25.00  1(+1)       512  (100)
VM-ID        STATE           VERSION PER ADMIN PRIV
 2 SYSTEM2   RUNNING         V20.0B  NO  NO    AG,AS
/show-vm-attributes vm-id=system2,information=*privileges
VM-ID        PRIV    DETAILS
 2 SYSTEM2   AG      *STDSET
             AS

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

(1)

The VM2000 administrator changes the attributes of VM2. The new CPU quota is 20. The maximum CPU utilization is 25. The ASSIGN-BY-GUEST for the assignment set *STDSET privilege is assigned to VM2.

(2)

The VM administrator queries the attributes and the details of the privileges for VM2.

Powered by Atlassian Confluence and Scroll Viewport.