subfunction causes data to be transferred from the source virtual storage to sink
virtual storage. The sink virtual machine can then respond with a REPLY subfunc
tion. The REPLY subfunction causes data to be transferred from specified sink
virtual storage to a REPLY buffer in the source virtual storage. The source virtual
machine then receives a response external interrupt indicating that theSEND /RECV request is complete.
When the source virtual machine executes theSEND /RECV function it specifies
the address and length of both theSEND buffer and REPLY buffer. The address
and length specifications are contained within the user parameter list
(VMCPARM). The user parameter list also contains a message ID and userid of
the user to receive the data(See the "VMCPARM Parameter List".) The source virtual machine can cancel a previously executed SEND /RECV request
provided the sink virtual machine has not yet executed the REPLY or REJECT
subfunction. If the sink virtual machine has already executed the RECEIVE sub
function, only the REPLY can be canceled (see"CANCEL: DIAGNOSE Code
X'68' Subfunction CodeX'0006"'). The sink virtual machine can execute the REJECT subfunction in response to the SEND /RECV request and cause the entire operation to be terminated (See "REJECT: DIAGNOSE Code X'68' Subfunction Code X'OOll "'.) The sink virtual machine can respond to a SEND /RECV request with the REPLY
subfunction without executing the RECEIVE subfunction. This has the effect of
informing the source virtual machine that the sink virtual machine cannot accept
data but that it can send data. The source virtual machine could have executed theSEND /RECV subfunction only as a means to solicit data from the sink virtual
machine. The application of this protocol is up to VMCF users. The user
doubleword can be used as a means to control such an application(See "VMCF User Doubleword".) You can execute a SEND /RECV request using the PRIORITY option. The PRI ORITY option causes the sink external interrupt for the SEND /RECV request to
be queued ahead of any other nonpriority external interrupts. Response external
interrupts directed to the source of a PRIORITY message are also queued in priori
tyorder.
SENDX: DIAGNOSE Code X'68' Subfunction Code X'0004'SENDX directs data to another virtual machine via a faster but more restrictive
protocol than theSEND subfunction. SENDX subfunction data reaches the sink
virtual machine at the same time theSEND external interrupt reaches the sink. In
order to use theSENDX subfunction, the sink virtual machine must have an
external interrupt buffer large enough to contain both the standard message header
and the data. The size of the external interrupt buffer is specified when you exe
cute theAUTHORIZE subfunction. Attempts to execute SENDX are rejected
when the sink virtual machine's external interrupt buffer is not large enough to con
tain the data. After the sink virtual machine receives theSEND external interrupt
and data, a response external interrupt is directed to the source virtual machine.
TheSENDX subfunction eliminates the need for a sink virtual machine to execute
a RECEIVE subfunction.
ASENDX request can be canceled by the source virtual machine provided the SENDX external interrupt has not yet been reflected to the sink virtual machine (See "CANCEL: DIAGNOSE Code X'68' Subfunction Code X'0006"'.) The Virtual Machine Communication Facility 95
virtual storage. The sink virtual machine can then respond with a REPLY subfunc
tion. The REPLY subfunction causes data to be transferred from specified sink
virtual storage to a REPLY buffer in the source virtual storage. The source virtual
machine then receives a response external interrupt indicating that the
When the source virtual machine executes the
the address and length of both the
and length specifications are contained within the user parameter list
(VMCPARM). The user parameter list also contains a message ID and userid of
the user to receive the data
provided the sink virtual machine has not yet executed the REPLY or REJECT
subfunction. If the sink virtual machine has already executed the RECEIVE sub
function, only the REPLY can be canceled (see
X'68' Subfunction Code
subfunction without executing the RECEIVE subfunction. This has the effect of
informing the source virtual machine that the sink virtual machine cannot accept
data but that it can send data. The source virtual machine could have executed the
machine. The application of this protocol is up to VMCF users. The user
doubleword can be used as a means to control such an application
be queued ahead of any other nonpriority external interrupts. Response external
interrupts directed to the source of a PRIORITY message are also queued in priori
tyorder.
SENDX: DIAGNOSE Code X'68' Subfunction Code X'0004'
protocol than the
virtual machine at the same time the
order to use the
external interrupt buffer large enough to contain both the standard message header
and the data. The size of the external interrupt buffer is specified when you exe
cute the
when the sink virtual machine's external interrupt buffer is not large enough to con
tain the data. After the sink virtual machine receives the
and data, a response external interrupt is directed to the source virtual machine.
The
a RECEIVE subfunction.
A