z/OS HCD User's Guide
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Possible actions on objects using the incremental update

z/OS HCD User's Guide
SC34-2669-00

Possible actions on objects using the incremental update

Table 5 shows what actions you can perform on objects by using the HCD incremental update function. The meaning of the markup is as follows:

x
Action possible, you can make the change.
—
Action not possible, you cannot make the change with the batch migration utility but must use the HCD dialog.
(x)
Action possible. These attributes are deleted when the object itself is deleted.
(—)
Action not possible. These attributes cannot be deleted because the object itself cannot be deleted.

See the notes below the table for further instructions on how to add, delete, or change certain objects, their attributes and connections.

Table 5. Actions on IODF Objects
Object/AttributesAddDeleteChange
Processor   
 ID x — —
 Type/model x(—) —
 Support level x(—) —
 Configuration mode x(—) —
 Serial number x — x
 Description x — x
 SNA address x — x
Channel Subsystem
 ID x — —
 Maximum Number Devices x — x
 Description x x x
Partition
 Name x x 1) x 11)
 Image number x(x) x11)
 Usage type x 10)(x) x
 Description x x x
PCIe function   
 FID x — —
 VF x — —
 UNIT x(x) x
 PCHID x x x
 PNETID x x x
 Partition x x x
 Description x x x
Channel path   
 CHPID x — —
 PCHID x x x 5)
 PNETID x x x
 Type x(—) x 5)
 Operation mode x(—) x 5)
 Access list x x x 5)
 Candidate list x x x 5)
 Dynamic switch x x x 5)
 Switch connection x x x 5; 15)
 CF connection x x x 5)
 Description x x x 5)
 OS parameter x x x 5)
 I/O cluster x x x 5)
Control unit   
 Number x x 2) x 4)
 Unit/model x(x) x
 Description x x x
 Serial number x x x
 Switch connection x x x 15)
 Channel paths x(x) x
 DLA x x x
 Logical address (CUADD) x x x
 Unit addresses x(x) x
 Protocol x x x
 IOCL x x x
Device   
 Number x x 3) x 4)
 Unit/model x(x) x
 Description x x x
 Serial number x x x
 Volume serial number x x x
 Control units x(x) x
 Processor connect x(x) x
 Unit address x(x) x
 Preferred CHPID x x x
 TIMEOUT x x x
 STADET x x x
 Candidate list x x x
 OS connect x — x
 Subchannel set x(x) x
 Parameters x x x
 Features x x x
 User parameters x x x
 PPRC usage x(x) x
Operating system   
 ID x — —
 Type x(—) —
 Description x — x
 D/R site OS x — x
EDT   
 ID x — —
 Description x — x
Esoteric   
 Name x — —
 VIO x(—) x
 Device list x x 6) x 7)
 Token x — x
Generic   
 VIO x(—) x
 Preference value x(—) x
Console   
 Device list x x 9) x 13)
 Order(x)(x) x
Switch   
 ID x — —
 Unit/model x(—) x
 Ports (installed range) x(—) x 8)
 Serial number x — x
 Description x — x
 Switch connection x x 14) x 15)
 Address x — x
Ports   
 ID x——
 Name x(—)x
 Occupied indicator x 15)x 15)n/a
Switch configuration   
 ID x——
 Description x—x
 Default connection x—x
Port configuration   
 Allowed connection x—x
 Prohibited connection x—x
 Dedicated connection x—x
 Blocked indicator xxn/a

References to IOCP and MVSCP in the following notes refer to data sets with extended syntax as described in Changing I/O configurations by editing data sets.

Notes:
  1. To delete a partition, specify all connected channel paths (defined via access or candidate lists) together with their attached I/O units without referring to the partition and without repeating the partition in the RESOURCE statement.
  2. A control unit is implicitly deleted, if its channel paths are respecified in the IOCP input data set together with their attached I/O units (except the control unit) and it no longer has any connection to a processor.
  3. A device is implicitly deleted, if its attaching control units are implicitly deleted using the incremental update specification, and there is no additional connection left to any control unit or operating system.
  4. To change control unit and device attributes, specify the entire logical control unit(s) (LCU) the control unit or device is part of. For migration to an OS configuration only (MVSCP data set), respecify the I/O device with the changed parameters. HCD will redefine the device in the corresponding subchannel set.
  5. To change channel path attributes, specify all logical control units the channel path is connected to in the IOCP input data set. Otherwise, the channel path is disconnected from the corresponding control units.
  6. To delete an esoteric device list, specify all device definitions in the MVSCP input data set, but do not connect them to the esoteric name.
  7. To add a device to an esoteric device list, specify the esoteric with the device number.

    To delete a device from the esoteric device list, specify the device in an IODEVICE statement) but do not specify the device number for the esoteric device list.

  8. An installed port can be set to uninstalled only if it does not belong to the minimum installed port range and does not hold a connection to a channel path or control unit.
  9. To delete a console list, specify all contained devices using the IODEVICE statement but do not include the devices in a NIPCON statement.
  10. If the usage type is not specified and you add a partition, the usage type is automatically defined: if the IOCP input data set contains a CF receiver channel path with the partition in its access or candidate list, the usage type is set to CF/OS, if not, the usage type is set to OS.
  11. To change the partition name or partition number specify the whole partition configuration including all channel paths with attached I/O units which have the partition in their access and candidate lists.
  12. (No longer used.)
  13. To change a complete console device list, use the NIPCON statement.

    To remove a single device from the console list, specify the corresponding IODEVICE statement and omit the NIPCON statement.

  14. To delete a switch-to-switch connection, specify a switch via a SWITCH statement and omit the switch-to-switch connection in the SWPORT parameter.
  15. When updating switch ports new connections always overwrite a previous connection or status. To be updated with an occupied status the port must currently not be connected.

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014