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

DEFINE MSGPROC<br />

►►<br />

DEFine<br />

Authorization<br />

Purpose<br />

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

MSGProc<br />

Usage Notes<br />

msgprocid<br />

VDEVice<br />

Privilege Class: G<br />

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

vdev<br />

DEVICES 4<br />

DEVices n<br />

SINGLE_message_path<br />

Use the DEFINE MSGPROC comm<strong>and</strong> to define a virtual message processor <strong>and</strong><br />

associated message devices in the issuer’s virtual I/O configuration. This comm<strong>and</strong><br />

establishes a coupling connection between a CFUSER defined user ID <strong>and</strong> the<br />

specified CF Service Machine running under z/<strong>VM</strong>.<br />

msgprocid<br />

specifies the user ID of a z/<strong>VM</strong> Virtual Machine that is defined to run as a<br />

Coupling Facility. <strong>CP</strong> will establish a coupling connection between the user ID<br />

that issues this comm<strong>and</strong> <strong>and</strong> the user ID specified by msgprocid.<br />

VDEVice vdev<br />

is the virtual device number of the base message device that you are defining<br />

to <strong>CP</strong>. The device number must be a 1 to 4 digit hexadecimal number between<br />

X'0000' <strong>and</strong> X'FFFC'. The virtual device number specified will be the first of four<br />

consecutive device numbers created. If the specified device number is not valid<br />

or if it or any of the next three consecutive device numbers are already defined,<br />

this comm<strong>and</strong> will fail.<br />

DEVices n<br />

specifies the number of message devices to be created in the coupling guest.<br />

The number of devices (n) must be an even number between 4 <strong>and</strong> 16<br />

inclusive; the default is 4.<br />

SINGLE_message_path<br />

will force only a single message path to be created for each message device.<br />

By default this comm<strong>and</strong> will create two message paths per message<br />

subchannel. Specifying SINGLE will turn off multi-path simulation when<br />

communicating with the Message Processor being defined.<br />

1. The user must be authorized to issue this comm<strong>and</strong> via the CFUSER oper<strong>and</strong><br />

on the OPTION Directory Control Statement in the user directory. Without<br />

authorization, the MSGProc oper<strong>and</strong> is rejected as not valid.<br />

2. If SPECIAL directory statements were used to define message processors for<br />

the user, then the user may specify only those msgprocids on the DEFINE<br />

MSGPROC comm<strong>and</strong>. Specifying a msgprocid not defined by the SPECIAL<br />

directory entry will cause the oper<strong>and</strong> to be rejected as not valid. The<br />

SPECIAL directory statement allows the system administrator to restrict which<br />

message processors that a user is allowed to define.<br />

►◄

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

Saved successfully!

Ooh no, something went wrong!