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.

MODIFY DEVICE / IODEVICE<br />

Usage Notes<br />

NOTDASD<br />

tells <strong>CP</strong> that this device is not a direct access storage device (DASD).<br />

TIME_Out<br />

tells <strong>CP</strong> that the I/O interface time out function is active for the following I/O<br />

interfaces between the channel <strong>and</strong> I/O device:<br />

v 4 second time out for initial selection<br />

v 30 second time out for data transfer.<br />

NOTIME_Out<br />

tells <strong>CP</strong> that the I/O interface time out function is not active for this device.<br />

PREFerred_channel_path nn<br />

tells <strong>CP</strong> to use this channel path in the specified or implied channel-subsystem<br />

image to initiate I/O requests before trying any other channel paths from the<br />

device that you are changing. The variable nn must be a 1- to 2-digit<br />

hexadecimal number between X'00' <strong>and</strong> X'FF'.<br />

Note: A preferred path must not be specified for a device connected to a<br />

control unit for which z/OS ® –managed paths are being used. Although<br />

the comm<strong>and</strong> will not prevent you from doing so, the use of preferred<br />

paths in a managed-path environment will adversely affect z/OS’s ability<br />

to manage channel-path workloads.<br />

NOPREFerred_channel_path<br />

tells <strong>CP</strong> that there is no preferred channel path.<br />

1. If you are using this comm<strong>and</strong> to modify I/O device characteristics, then you<br />

must specify one of each of the I/O device characteristics (IODC), because this<br />

comm<strong>and</strong> does not accept defaults <strong>and</strong> will not carry over any previous IODC<br />

characteristics definitions.<br />

For example, suppose you used the following comm<strong>and</strong> to define a new DASD:<br />

define device 16d9 unit_address a3 cu 501 dasd<br />

In this comm<strong>and</strong>, you specified one IODC characteristic, DASD. You took the<br />

defaults for the other three: no preferred channel path, no status verification,<br />

<strong>and</strong> no time out function.<br />

If you want to change the DASD to another device <strong>and</strong> retain the previous<br />

IODC characteristic definitions, you must specify exactly what you want:<br />

mod dev 16d9 unit_addr a3 cu 501 nostat notdasd notime_out nopref<br />

Note: This is especially true for DASD devices. If you are modifying the IODC<br />

characteristics of a DASD, you must specify DASD in your comm<strong>and</strong>. If<br />

you do not, the DASD will not work as expected.<br />

2. 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 />

612 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><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.

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

Saved successfully!

Ooh no, something went wrong!