Return
Code
1
Meaning
Invalid virtual buffer address or length. A virtual machine attempted to execute a
VMCF sub function but specified an invalid address or length: • External interrupt buffer n,ot within virtual storage. • External interrupt buffer address not doubleword aligned. • Message data or buffer not within virtual storage. • External interrupt buffer less than the standard message header length.
2 Invalid sub function code. A virtual machine attempted to execute a VMCF sub­
function but specified an unsupported subfunction code.
3 Protocol violation. A virtual machine attempted to execute a sub function which
would violate the defined protocol: • Cancel a message it did not originate. • Reply to a message not sent via SEND /RECV. • Executed more than one RECEIVE to a SEND or SEND /RECV request.
4 Source virtual machine not authorized. A virtual machine attempted to execute a
subfunction (other than AUTHORIZE) but was not authorized to use VMCF (had
not successfully executed the AUTHORIZE subfunction).
5 User not available. A virtual machine attempted to execute a function and speci­
fied a virtual machine currently not available for VMCF communication: • Not logged on. • Not authorized for VMCF communication. • Virtual machine authorized SPECIFIC for some other virtual machine.
6 Protection violation. A virtual machine attempted to execute a VMCF function
that would result in a STORE or FETCH protection violation. The virtual
machine specified a data or buffer address that contained a storage key other than
its current PSW key (assume key was nonzero). This return code is also set if a
virtual machine attempts to receive data in a CP-owned shared segment.
7 SENDX data too large. A virtual machine attempted to execute a SENDX request
but specified a SENDX data length larger than the sink virtual machine external
interrupt buffer.
8 Duplicate message. A virtual machine attempted to execute a SEND-type function
and specified a message ID and virtual machine userid for which there was already
an active message.
9 Target virtual machine in QUIESCE status. A virtual machine attempted to exe­
cute a SEND-type function and specified a sink virtual machine userid of a virtual
machine in QUIESCE status. 10 Message limit exceeded. A virtual machine attempted to execute a SEND subfunc­
tion but already had 50 messages active. The virtual machine should clear any
pending RESPONSE external interrupts or CANCEL previously sent messages in
order to continue processing.
Figure 12 (Part 2 of 3). DIAGNOSE Code X'68' Return Codes
The Virtual Machine Communication Facility 107

Return
Code Meaning
11 REPLY canceled. The source virtual machine executed a CANCEL to a previous
SEND /RECV request. The sink virtual machine had already RECEIVED the
message but had not yet executed a REPLY. The sink virtual machine REPLY in
this case is canceled. The sink virtual machine receives return code 12 (message
not found) when it executes the REPL Y subfunction.
12 Message not found. A virtual machine attempted to execute a sub function and
specified a message ID and virtual machine userid for a message that does not
exist. The message may have existed at one time but could have been cancelled by
the originator.
13 Synchronization error. The sink virtual machine attempted to respond to a mes-
sage for which it had not yet received the SEND external interrupt. This condition
can occur if the sink virtual machine is anticipating certain messages but does not
wait for the SEND external interrupt.
14 CANCEL too late. A virtual machine attempted to CANCEL a message that had
already been processed. The sink virtual machine had already responded with
RECEIVE or REJECT (SEND request) or REPLY or REJECT (SEND/RECV
request). This return code is also set if a virtual machine attempts to CANCEL a
SENDX request for which the sink virtual machine had already received the SEND
external interrupt.
15 Paging I/O error. A virtual machine attempted to execute a subfunction which
resulted in an uncorrectable paging I/O error. This is a hardware failure.
16 Incorrect length. A virtual machine executed a RECEIVE or REPL Y function and
specified a RECEIVE buffer length less than the source virtual machine SEND
data length or a REPL Y data length larger than the source virtual machine REPL Y
buffer length. The source virtual machine receives a data transfer return code
identifying the condition.
17 Destructive overlap. A virtual machine executed a RECEIVE or REPL Y function
and specified a RECEIVE buffer address which overlapped the source virtual
machine SEND data address or a REPL Y data address that overlapped the source
virtual machine REPL Y buffer address. This condition can occur only when a vir-
tual machine is sending messages to itself (a "wrap connection"). 18 User not authorized for PRIORITY messages. A virtual machine attempted to
send a PRIORITY message to a virtual machine that was not authorized to accept
PRIORITY messages (that is, had not executed the AUTHORIZE function with
the PRIORITY option).
19 Data transfer error. A virtual machine executed a request that resulted in a data
transfer error condition associated with the other virtual machine. The return code
is returned to the sink virtual machine to indicate that the transaction did not com-
plete successfully. 20 CANCEL -busy. A virtual machine attempted to cancel a message being proc-
essed. If this is a SEND /RECV request and the RECEIVE sub function is in
process, repeated retries may cancel the REPL Y subfunction.
Figure 12 (Part 3 of 3). DIAGNOSE Code X'68' Return Codes 108 VM/SP System Programmer's Guide