HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_RECEIVE and RECEIVE Verbs
The local TP is now in Confirm_Deallocate state, so it will normally issue the [MC_]CONFIRMED verb to
confirm deallocation of the conversation.
AP_CONFIRM_SEND (half-duplex conversation only)
The partner TP issued the [MC_]PREPARE_TO_RECEIVE verb with ptr_type and dealloc_type parameters
indicating that confirmation was required, or issued the [MC_]SEND_DATA verb with a send type of
PREPARE_TO_RECEIVE_CONFIRM. The local TP is now in Confirm_Send state, so it will normally issue
the [MC_]CONFIRMED verb to confirm the state change and then begin to send data.
AP_CONFIRM_WHAT_RECEIVED (half-duplex conversation only)
The partner TP issued the [MC_]CONFIRM verb, or issued the [MC_]SEND_DATA verb with a send type
of CONFIRM. The local TP is now in Confirm state, so it will normally issue the [MC_]CONFIRMED verb.
The following values will only be returned if the local TP specified
AP_YES for the rtn_status (return status with
data) parameter:
AP_DATA_SEND, AP_DATA_COMPLETE_SEND, AP_UC_DATA_COMPLETE_SEND,
AP_PS_HDR_COMPLETE_SEND
The partner TP sent data and then issued the [MC_]PREPARE_TO_RECEIVE verb without requesting
confirmation, or issued the [MC_]SEND_DATA verb with a send type of PREPARE_TO_RECEIVE. The
local TP is now in Send_Pending state, so it will normally begin to send data.
AP_DATA_CONFIRM_DEALLOCATE, AP_DATA_COMPLETE_CONFIRM_DEALL,
AP_UC_DATA_COMPLETE_CNFM_DEALL, AP_PS_HDR_COMLETE_CNFM_DEALL
All of these values apply only to half-duplex conversations.
The partner TP sent data and then issued the [MC_]DEALLOCATE verb with a dealloc_type parameter
indicating that confirmation was required, or issued the [MC_]SEND_DATA verb with a send type
of DEALLOCATE. The local TP is now in Confirm_Deallocate state, so it will normally issue the
[MC_]CONFIRMED verb to confirm deallocation of the conversation.
AP_DATA_CONFIRM_SEND, AP_DATA_COMPLETE_CONFIRM_SEND,
AP_UC_DATA_COMPLETE_CNFM_SEND, AP_PS_HDR_COMPLETE_CNFM_SEND
All of these values apply only to half-duplex conversations.
The partner TP sent data and then issued the [MC_]PREPARE_TO_RECEIVE verb with ptr_type and
dealloc_type parameters indicating that confirmation was required, or issued the [MC_]SEND_DATA verb
with a send type of PREPARE_TO_RECEIVE_CONFIRM. The local TP is now in Confirm_Send state, so
it will normally issue the [MC_]CONFIRMED verb to confirm the state change and then begin to send data.
AP_DATA_CONFIRM, AP_DATA_COMPLETE_CONFIRM, AP_UC_DATA_COMPLETE_CONFIRM,
AP_PS_HDR_COMPLETE_CONFIRM
All of these values apply only to half-duplex conversations.
The partner TP sent data and then issued the [MC_]CONFIRM verb, or issued the [MC_]SEND_DATA
verb with a send type of CONFIRM. The local TP is now in Confirm state, so it will normally issue the
[MC_]CONFIRMED verb.
In all CONFIRM cases above, the TP may issue the [MC_]SEND_ERROR verb instead of the
[MC_]CONFIRMED verb, to indicate that an error was detected in the supplied data or in pro-
cessing. If it issues [MC_]SEND_ERROR in Send_Pending state (after receiving
AP_DATA_SEND,
AP_DATA_COMPLETE_SEND
, AP_UC_DATA_COMPLETE_SEND,orAP_PS_HDR_COMPLETE_SEND), it can
specify whether the error was detected in the supplied data, or in its own data or processing. For more
information, see the description of the [MC_]SEND_ERROR verb in Section 4.17, MC_SEND_ERROR and
SEND_ERROR.
4.9.3 End of Data
If the local TP issues one of the basic-conversation RECEIVE verbs and sets the fill parameter to AP_BUFFER, the
receipt of data ends when max_len or end of data is reached. End of data is indicated by either of the following:
159