MODIFY-VM-DEVICE-ATTRIBUTES (Modify device attributes)

/MODIFY-VM-DEVICE-ATTRIBUTES is used to specify whether the specified devices can also be assigned implicitly to a VM by a guest system.

For this purpose devices have the device attribute ASSIGN-BY-GUEST. The default setting is ASSIGN-BY-GUEST=*NO, i.e. the devices can initially not be assigned implicitly by a VM’s guest system.

The default setting for this device attribute can be modified for SU /390 in the VM2000 parameter file (see "Setting the VM2000 parameters in the parameter service").

The default setting for this device attribute can be modified for selected devices or for all existing devices using /MODIFY-VM-DEVICE-ATTRIBUTES UNITS=... and for all new devices using /MODIFY-VM-DEVICE-ATTRIBUTES UNITS=*NEW-DEVICES. New devices (see "Dynamic I/O configuration modification") then assume the new setting as a device attribute.

DUMMY tape devices should not be assigned implicitly, see "Special devices".

Virtual consoles cannot be assigned implicitly by a guest system. Alias devices (PAV/DPAV) and CRD devices may only be assigned implicitly (the attribute is ignored for these devices).

The usage mode of a device does not change with this command (see "MODIFY-VM-DEVICE-USAGE (Modify usage mode of the devices of a VM)").

A message is only issued for a device in the event of an error.

This command is reserved for the VM2000 administrator.

 

MODIFY-VM-DEVICE-ATTRIBUTES

UNITS = *ALL / *NEW-DEVICES / *PUBSET-DEVICES(...) / *BY-ASSIGNMENT-SET(...) /
				list-poss(28): *DEVICE-RANGE(...) / <alphanum-name 1..4 with-wild(20)>
	*PUBSET-DEVICES(...)
		|	PUBSET = *BY-PUBRES-DEVICE(...) / <cat-id 1..4>
		|		*BY-PUBRES-DEVICE(...)
		|			|	UNIT = <alphanum-name 2..2> / <x-text 4..4>
	*BY-ASSIGNMENT-SET(...)
		|	SET-NAME = *STDSET / <name 1..8>
	*DEVICE-RANGE(...)
		|	FROM = <alphanum-name 2..2> / <x-text 4..4>
		|	,TO = <alphanum-name 2..2> / <x-text 4..4>
,ASSIGN-BY-GUEST = *NO / *YES(...)
	*YES(...)
		|	SET-NAME = *STDSET / <name 1..8>

UNITS =
Specifies the devices to be assigned the attribute.

The setting for new devices can only be modified using UNITS=*NEW-DEVICES.

UNITS = *ALL
The attribute is to be assigned to all existing devices.

UNITS = *NEW-DEVICES
The attribute is to be assigned to all new devices (dynamic I/O configuration modification).

UNITS = *PUBSET-DEVICES(...)
The attribute is to be modified for all the devices of a pubset.

See also "Notes on pubset specification in the VM2000 commands" and "Pubset reconfiguration".

PUBSET = *BY-PUBRES-DEVICE(...)
Determines the devices of the pubset by means of the pubres device.

UNIT = <alphanum-name 2..2> / <x-text 4..4>
Mnemonic device name of the pubres device.

PUBSET = <cat-id 1..4>
Catalog ID of the pubset. The pubset must be entered together with its pubres device in the monitor system’s MRS catalog.

UNITS = *BY-ASSIGNMENT-SET(...)
The attribute is to be modified for all devices of an assignment set.

SET-NAME = *STDSET / <name 1..8>
Determines the devices of the assignment set by means of the set name.

UNITS = *DEVICE-RANGE(...)
All the devices in this name range are to be assigned the attribute.

Device names <x-text 4..4> (in *DEVICE-RANGE) are selected from FROM to TO in hexadecimal order. Otherwise, device names <alphanum-name 2..2> are selected in alphabetical order.

FROM = <alphanum-name 2..2> / <x-text 4..4>
Defines the start of the name range.

TO = <alphanum-name 2..2> / <x-text 4..4>
Defines the end of the name range. The mnemonic device name must be in the same value range (2- or 4-digit mn) as the FROM device name and must be greater than or equal to the FROM device name in ascending order in the value range.

UNITS = <alphanum-name 1..4 with-wild(20)>
Specifies the devices to be assigned the attribute.

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

ASSIGN-BY-GUEST = *NO
Device assignment may not be executed implicitly by the guest system, but only using the VM2000 command /ADD-VM-DEVICES or /SWITCH-VM-DEVICES or (for VM definitions) using /CREATE- or /MODIFY-VM-DEFINITION.
Exception: Alias devices (PAV/DPAV, see "Parallel access volume (PAV, SU /390)"), CRD devices (see "Special devices") and snap units for Snapsets (see "Special devices").

ASSIGN-BY-GUEST = *YES(...)
Device assignment can also be executed implicitly by the guest system.

SET-NAME = *STDSET / <name 1..8>
The selected devices are assigned to the specified assignment set.

 

Command return codes

(SC2)   SC1	Main code	Meaning
0 1             0 2             0 2             0 2             0 64 64 64 64 64 64	CMD0001 VMS4180 VMS4203 VMS4241 VMS4242 VMS3002 VMS4006 VMS4171 VMS4200 VMS4223 VMS9005	Command successfully executed Specified set of devices empty No devices are assigned to the assignment set Attribute not changed for all devices of the pubset Attribute changed only for the pubres device of the pubset Invalid operand value (e.g. *DEVICE-RANGE operand) Device not available ASSIGN-BY-GUEST is not possible for virtual consoles Assignment set not yet created Command not executed (operand *PUBSET-DEVICES) Command could not be processed or could only be partially processed

Guaranteed messages

VMS4171

Only if *PUBSET-DEVICES is specified:  VMS4223, VMS4240, VMS4241, VMS4242

Only if UNITS is specified without *DEVICE-RANGE and without wildcards:  VMS4006

Example

/modify-vm-device-attributes units=*pubset-devices(pubset=vm04),
                              assign-by-guest=*yes(set-name=sys2impl) —  (1)
VMS4240 DEVICE ATTRIBUTES OF PUBSET 'VM04' WITH PUBRES DEVICE 'D4' MODIFIED

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

(1)	The VM2000 administrator specifies the ASSIGN-BY-GUEST attribute for the pubset with the pubres device D4 and assigns the pubset devices to the assignment set SYS2IMPL.

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

See also the detailed examples for device and pubset management ("Example of peripheral device management" and "Example of pubset management").