HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_CONFIRM and CONFIRM
Parameter Check
If the verb does not execute because of a parameter error, APPC returns the following parameters:
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_TP_ID
The value of tp_id did not match a TP identifier assigned by APPC.
AP_CONFIRM_INVALID_FOR_FDX
The local TP attempted to use the [MC_]CONFIRM verb in a full-duplex conversation. This verb can
be used only in a half-duplex conversation.
AP_CONFIRM_ON_SYNC_LEVEL_NONE
The local TP attempted to use the [MC_]CONFIRM verb in a conversation with a synchronization
level of
AP_NONE. The synchronization level, established by the [MC_]ALLOCATE verb, must be
AP_CONFIRM_SYNC_LEVEL.
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.
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_CONFIRM_BAD_STATE
The conversation was not in Send or Send_Pending state.
AP_CONFIRM_NOT_LL_BDY
(Returned for basic-conversation CONFIRM only) The conversation for the local TP was in Send state,
and the local TP 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
122