HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_RECEIVE_AND_WAIT and RECEIVE_AND_WAIT
what_rcvd parameter
New state
AP_SEND
Send
AP_DATA_SEND
AP_DATA_COMPLETE_SEND
Send_Pending
primary_rc
New state
AP_PARAMETER_CHECK
AP_STATE_CHECK
AP_CONVERSATION_TYPE_MIXED
AP_INVALID_VERB
AP_INVALID_VERB_SEGMENT
AP_STACK_TOO_SMALL
AP_TP_BUSY
AP_UNEXPECTED_DOS_ERROR
No change
AP_CONV_FAILURE_RETRY
AP_CONV_FAILURE_NO_RETRY
Reset
AP_DEALLOC_ABEND
AP_DEALLOC_ABEND_PROG
AP_DEALLOC_ABEND_SVC
AP_DEALLOC_ABEND_TIMER
Reset
AP_DEALLOC_NORMAL
Reset
AP_PROG_ERROR_PURGING
AP_PROG_ERROR_NO_TRUNC
AP_SVC_ERROR_PURGING
AP_SVC_ERROR_NO_TRUNC
AP_PROG_ERROR_TRUNC
AP_SVC_ERROR_TRUNC
Receive (half-duplex conversation) or no change (full-duplex
conversation)
4.11.9 Usage Notes
This section provides additional usage information about the following topics:
• PS header data
• Avoiding indefinite waits
PS Header Data
UNIX
In a conversation with a synchronization level of AP_SYNCPT, the received data may be in PS Header format. In
a mapped conversation, this is indicated by the value of the what_rcvd parameter; in a basic conversation, this is
indicated by an LL field of 0x0001 (for more information, see Section 2.11.1, Logical Records). The Syncpoint
Manager is responsible for converting the data into the appropriate Syncpoint commands.
Avoiding Indefinite Waits
If the local TP issues the [MC_]RECEIVE_AND_WAIT verb, it will be suspended until information is received
from the partner TP. It could wait indefinitely if the partner TP does not send any information, or does
not issue a verb causing the partner LU to flush its send buffer. If you need to have the TP operating
continuously, use the [MC_]RECEIVE_AND_POST verb but avoid waiting on the callback routine, or use the
[MC_]RECEIVE_IMMEDIATE verb.
184