|
|
|
|
In Using APPC Verbs to Change Conversation States, the conversation states appear in the left and right margins. This table shows how APPC verbs can change the state of the conversation from Send to Receive and from Receive to Send.
Before the conversation is allocated, the state is Reset for both TPs. After the conversation is allocated, the initial state is Send for the invoking TP and Receive for the invoked TP.
The MC_PREPARE_TO_RECEIVE verb enables a TP to change the conversation from Send to Receive state. This verb does the following:
Flushes the local LU's send buffer.
Sends the AP_CONFIRM_SEND indicator to the partner TP through the what_rcvd parameter of a receive verb. This indicator tells the partner TP that an MC_CONFIRMED response is expected before the partner TP can begin to send data.
Performs confirmation processing because the following conditions are true:
The synchronization level of the conversation is set to
The parameter ptr_type is set to
Issuing the MC_RECEIVE_AND_WAIT verb while the conversation is in Send state also flushes the LU's send buffer and changes the conversation state to Receive. Changing the conversation state in this manner does not support confirmation processing.
The MC_REQUEST_TO_SEND verb informs the partner TP (for which the conversation is in Send state) that the local TP (for which the conversation is in Receive state) wants to send data.
This request is communicated to the partner TP through the rts_rcvd parameter of the MC_CONFIRM verb. (The rts_rcvd parameter is also returned to MC_SEND_DATA and other verbs.)
When the partner TP issues the MC_PREPARE_TO_RECEIVE verb, the conversation state changes to Receive for the partner TP, making it possible for the local TP to send data.
Issuing the MC_REQUEST_TO_SEND verb does not change the state of the conversation. Upon receiving a request to send, the partner TP is not required to change the conversation state; it can ignore the request.
|
|
|
|
|