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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DEFINE CU / CNTLUNIT<br />

Oper<strong>and</strong>s<br />

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

nnnn<br />

is the number of the control unit that you are defining. The variable nnnn must<br />

be a 1- to 4-digit hexadecimal number between X'0000' <strong>and</strong> X'FFFE'.<br />

TYpe<br />

is the control unit type. Valid types are:<br />

Dci<br />

tells <strong>CP</strong> that this control unit uses the directed-coupled interlock (DCI) protocol.<br />

DCI protocol is a method of data transfer up to 1.5 megabytes per second. DCI<br />

protocol requires the sender to raise a signal on the interface along with the<br />

byte of data being transferred. The signal <strong>and</strong> data must be maintained until the<br />

receiver acknowledges receipt of the data.<br />

STREAM3<br />

S tells <strong>CP</strong> that this control unit uses a method of data transfer up to 3 megabytes<br />

per second. This protocol does not interlock data streaming between sender<br />

<strong>and</strong> receiver. Once the data transfer begins, the sender does not wait for<br />

acknowledgement from the receiver before sending the next byte of data. The<br />

control unit determines the actual data transfer rate.<br />

STREAM4.5<br />

S4<br />

tells <strong>CP</strong> that this control unit uses a method of data transfer up to 4.5<br />

megabytes per second. This protocol does not interlock data streaming between<br />

sender <strong>and</strong> receiver. Once the data transfer begins, the sender does not wait<br />

for acknowledgement from the receiver before sending the next byte of data.<br />

The control unit determines the actual data transfer rate.<br />

TYPE_2<br />

UNSHARED<br />

tells <strong>CP</strong> that this control unit supports concurrent multiple I/O requests. This<br />

means that this control unit is synonymous with a Type 2 control unit.<br />

SHARED<br />

TYPE_1<br />

tells <strong>CP</strong> that this control unit only supports one I/O request at a time. This<br />

means that this control unit is synonymous with a Type 1 control unit.<br />

ESCON<br />

tells <strong>CP</strong> that this control unit uses the Enterprise Systems Connection (ESCON)<br />

channel to control unit I/O interface to transmit data through optical cables. Also<br />

specify this oper<strong>and</strong> for control units attached through direct-system-device<br />

(DSD), emulated-I/O (EIO), FICON converter (FCV) or internal-system-device<br />

(ISD) channel paths.<br />

FICON_CTC<br />

tells <strong>CP</strong> that the control unit is a channel-to-channel (CTC) adapter on a FICON<br />

channel path. At least one of the two sides of a FICON CTC connection must<br />

have a FICON CTC control unit defined. If a FICON CTC control unit is defined<br />

on both sides (which is recommended), the two connected channels determine<br />

which side acts as the control unit at any given time. For a FICON CTC<br />

control-unit definition to be effective, the FICON CTC facility must be installed in<br />

the host with the control-unit definition<br />

* indicates that the correct TYpe will be chosen automatically. Automatic selection<br />

applies to control units attached through DSD, EIO, CNC, CVC, CBY, CTC, FC,<br />

F<strong>CP</strong>, FCV, IQD, or ISD channel paths.

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

Saved successfully!

Ooh no, something went wrong!