LU 6.2 API Application Programmer's Reference Guide (30294-90008)

116 Chapter5
Intrinsic Descriptions
MCRcvNoWait
in the Length parameter. When the final portion of a
data record is received, the
WhatReceived parameter
returns 1 (DATA_COMPLETE).
4 = SEND
Indicates that the remote TP has issued the equivalent
of MCPrepToRcv or MCRcvAndWait and has entered
Receive state. The local TP is now in Send state and can
issue only those intrinsics that are callable from Send
state.
5 = CONFIRM
Indicates that the remote TP has issued the equivalent
of MCConfirm, placing the local TP in Confirm state.
Unless it detects an error, the local TP must respond
with a call to MCConfirmed.
6 = CONFIRM_SEND
Indicates that the remote TP has issued the equivalent
of MCPrepToRcv with a synchronization level of
CONFIRM. The local TP is placed in Confirm Send
state. Unless it detects an error, it must send a
confirmation response to the remote and enter Send
state.
7 = CONFIRM_DEALLOCATE
Indicates that the remote TP has issued the equivalent
of MCDeallocate with a synchronization level of
CONFIRM. The local TP is placed in Confirm
Deallocate state. Unless it detects an error, it must
send a confirmation response to the remote TP and call
MCDeallocate with a DeallocateType of LOCAL.
When the remote TP deallocates normally, a status info
value of +100 is returned to the local TP.
Status
Required; 32-bit signed integer; output. Indicates the
result of intrinsic execution. See the “Status
Parameter” section, earlier in this chapter, for more
information.
Description
The MCRcvNoWait intrinsic receives any data that has arrived in the
receive buffer for the specified conversation. It differs from the
MCRcvAndWait intrinsic in the following ways: