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

Chapter 4 51
Conversation States
Send State
Send State
In Send state, a TP controls the conversation. A TP in Send state stays
in Send state unless it requests to enter another state or the remote TP
detects an error and forces the local TP to enter another state.
Table 4-3 lists all the intrinsics that can be called from Send state. It
also indicates what state the local TP is in after each intrinsic executes
successfully. Notice that MCRcvAndWait can place the local side of the
conversation in several different states, depending on the type of
information it receives from the remote TP.
The MCDeallocate and MCTest intrinsics have certain parameters
listed with them, because only calls with those parameters are allowed
in Send state. See the descriptions of MCDeallocate and MCTest in
Chapter 5 , “Intrinsic Descriptions,” for more information.
Table 4-3 Send State Intrinsics
Intrinsic State Entered
Upon Successful
Execution
MCConfirm Send
MCDeallocate
DeallocateType=
{ 1 (FLUSH) }
{ 2 (ABEND) }
{ 6 (CONFIRM) }
Reset
MCErrMsg Send
MCFlush Send
MCGetAttr Send
MCPrepToRcv Receive
MCRcvAndWait
WhatReceived=
{ 1 (DATA_COMPLETE) }
{ 2 (DATA_INCOMPLETE) }
{ 4 (SEND) }
{ 5 (CONFIRM) }
{ 6 (CONFIRM_SEND) }
{ 7 (CONFIRM_DEALLOCATE) }
Receive
Receive
Send
Confirm
Confirm Send
Confirm Deallocate
MCSendData Send
MCSendError Send
MCTest Test = 1 (REQUEST_TO_SEND_RECEIVED Send