HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_RECEIVE_AND_WAIT and RECEIVE_AND_WAIT
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_BAD_CONV_ID
The value of conv_id did not match a conversation identifier assigned by APPC.
AP_BAD_RETURN_STATUS_WITH_DATA
The rtn_status parameter was set to a value that was not valid.
AP_BAD_TP_ID
The value of tp_id did not match a TP identifier assigned by APPC.
UNIX
AP_INVALID_FORMAT
The reserved field format was set to a nonzero value.
AP_SYNC_NOT_ALLOWED
The application issued this verb within a callback routine, using the synchronous APPC entry point.
Any verb issued from a callback routine must use the asynchronous entry point.
WINDOWS
AP_INVALID_DATA_SEGMENT
The data was longer than the allocated data segment, or the address of the data buffer was incorrect.
AP_RCV_AND_WAIT_BAD_FILL
This return code applies only to the basic-conversation RECEIVE_AND_WAIT verb. The fill parameter
was set to a value that was not valid.
State Check
If the conversation is in the wrong state when the TP issues this verb, APPC returns the following parameters:
primary_rc
AP_STATE_CHECK
secondary_rc
Possible values are:
AP_RCV_AND_WAIT_BAD_STATE
The conversation was not in Receive, Send, or Send_Pending state when the TP issued this verb.
AP_RCV_AND_WAIT_NOT_LL_BDY
This return code applies only to the basic-conversation RECEIVE_AND_WAIT verb. The conversation
was in Send state; the TP began but did not finish sending a logical record.
Other Conditions
If the verb does not execute because other conditions exist, APPC returns primary return codes (and, if applicable,
secondary return codes). For information about these return codes, see Appendix B, Common Return Codes.
Possible return codes are:
primary_rc
181