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

►►<br />

DEFine<br />

CU<br />

CNTLUNIT<br />

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

UNIT_Address<br />

(3)<br />

UNITADD<br />

Authorization<br />

Purpose<br />

nnnn<br />

nn<br />

nn-nn<br />

Link Address(es):<br />

Notes:<br />

(4)<br />

LINK_address<br />

▼<br />

aa<br />

ddaa<br />

*<br />

TYpe<br />

UNSHARED<br />

TYPE_2<br />

Dci<br />

STREAM3 SHARED<br />

S<br />

TYPE_1<br />

STREAM4.5<br />

S4<br />

ESCON<br />

FICON_CTC<br />

*<br />

OPEN_SYStems_adapter<br />

OSA<br />

(1)<br />

CF<br />

Link Address(es)<br />

(5) (6) (7)<br />

CU_LOGICal_address<br />

CUADD<br />

Privilege Class: B<br />

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

CU_LOGICal_address<br />

CUADD<br />

1 The old form of this oper<strong>and</strong>, CFS, is still supported for compatibility.<br />

2 You can specify a maximum of 8 channel path IDs.<br />

nn<br />

CHPID<br />

PATH<br />

3 For control units attached through EIO channel paths, only one unit address may be specified.<br />

(2)<br />

▼ nn<br />

4 If linking to a switch, you must specify the LINK_ADDRESS <strong>and</strong> optionally the CU_LOGICAL_ADDRESS oper<strong>and</strong>s.<br />

nn<br />

Use DEFINE CU or CNTLUNIT to define a new control unit to the I/O configuration.<br />

Note: DEFINE CU <strong>and</strong> DEFINE CNTLUNIT are dynamic I/O comm<strong>and</strong>s. Dynamic<br />

I/O configuration is only supported on System/390 ®<br />

<strong>and</strong> zSeries processors.<br />

If your system is not running on one of these processors, your comm<strong>and</strong> will<br />

not complete successfully.<br />

CSS 0<br />

CSS<br />

nn<br />

DEFINE CU / CNTLUNIT<br />

MANaged_paths<br />

5 For control units attached through DSD channel paths, CUADD is optional <strong>and</strong> defaults to 0 if only one control unit is defined. If CUADD is specified for<br />

these control units, it should have the value 0, 1, or 2 with a LINK_address of 0.<br />

6 For control units attached through EIO channel paths, CUADD is ignored <strong>and</strong> the value is automatically set to the same value as that specified in the<br />

UNITADD parameter.<br />

7 For FICON CTCs on a shared channel path, the CUADD parameter specifies the partition number of the destination partition; that is, the remote end of<br />

the CTC connection for the control unit being defined. A control unit must be defined for each destination partition on the shared channel path. For<br />

FICON CTCs on non-shared channel paths, the destination partition is implicit in the channel-path definition <strong>and</strong> should not be specified here.<br />

n<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 149<br />

►◄

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

Saved successfully!

Ooh no, something went wrong!