27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DELETE DEVICE / IODEVICE<br />

Usage Notes<br />

Responses<br />

Note: This parameter <strong>and</strong> other parameters that identify different<br />

channel-subsystem IDs require that the logical channel-subsystem facility<br />

be installed.<br />

1. Before you delete one or more real devices from your I/O configuration, they<br />

must all be offline <strong>and</strong> their corresponding subchannels must also be offline. To<br />

take a device offline, use the VARY (Real Device) comm<strong>and</strong>. (See page 1710.)<br />

To take a subchannel offline, use the VARY SUBCHANNEL comm<strong>and</strong>.(See<br />

page 1714.)<br />

2. On a machine with multiple logical channel-subsystem images, the DELETE<br />

DEVICE <strong>and</strong> DELETE IODEVICE comm<strong>and</strong>s delete the device with respect to<br />

the control unit’s connection to channel paths within the single specified logical<br />

channel-subsystem image. To delete devices from more than one logical<br />

channel-subsystem image, you must enter a separate DELETE DEVICE or<br />

DELETE IODEVICE comm<strong>and</strong> for each logical channel-subsystem image from<br />

which you want the devices deleted.<br />

3. When you delete one or more real devices from your I/O configuration, <strong>CP</strong> also<br />

deletes their corresponding real device blocks (RDEVs). If you want to delete<br />

the RDEV but do not want to change the I/O configuration, use the DELETE<br />

RDEVICE comm<strong>and</strong>.(See page 228.)<br />

4. After successfully entering this comm<strong>and</strong>, you will have changed the software’s<br />

view of the I/O configuration <strong>and</strong> part of the hardware’s view: the active I/O<br />

configuration in the hardware system area (HSA). You should also change the<br />

other part of the hardware’s view: the active I/O configuration data set (IOCDS)<br />

file on the support element (SE) hard disk.<br />

To change the IOCDS file on the SE hard disk, you must:<br />

a. Update the IO<strong>CP</strong> source file.<br />

b. Run the IO<strong>CP</strong> utility (see page 1849) against the updated IO<strong>CP</strong> file. If the<br />

IO<strong>CP</strong> utility runs without errors, it downloads the new IOCDS file to the SE<br />

hard disk.<br />

c. Issue the SET IOCDS_ACTIVE comm<strong>and</strong> (see page 1258) to make the new<br />

IOCDS file the active file that the processor will use during the next<br />

power-on reset (POR).<br />

5. To define a new device on the system, use the DEFINE DEVICE or IODEVICE<br />

comm<strong>and</strong>. (See page 155.)<br />

6. To change the definition of an existing device on the system, use the MODIFY<br />

DEVICE or IODEVICE comm<strong>and</strong>.(See page 610.)<br />

7. To display the status of one or more real devices, use the QUERY (Real<br />

Device) comm<strong>and</strong>. (See page 955.)<br />

Note: If your processor is in LPAR mode, the QUERY (Real Device) comm<strong>and</strong><br />

displays the status of the device only if you issue the QUERY comm<strong>and</strong><br />

in a logical partition (LP) that has been defined to have access to the<br />

device.<br />

Response 1:<br />

224 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

To delete 4 real devices from your I/O configuration, enter the following:<br />

delete device 300-303 unit_address 00 cu_number 300<br />

Device configuration change completed successfully<br />

RDEV 0300 deleted

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!