HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_SEND_DATA and SEND_DATA
Possible values are:
AP_BAD_CONV_ID
The value of conv_id did not match a conversation identifier assigned by APPC.
AP_BAD_LL
This return code applies only to the SEND_DATA verb. The logical record length field of a logical
record contained a value that was not valid—
0x0000, 0x0001, 0x8000,or0x8001. For more
information, see Section 2.11.1, Logical Records.
AP_BAD_TP_ID
The value of tp_id did not match a TP identifier assigned by APPC.
WINDOWS
AP_INVALID_DATA_SEGMENT
The data was longer than the allocated data segment, or the address of the data buffer was incorrect.
AP_SEND_DATA_INVALID_TYPE
The type parameter was set to a value that was not valid.
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.
AP_SEND_TYPE_INVALID_FOR_FDX
The application issued this verb in a full-duplex conversation, but the type parameter specified a send
type that was not valid in a full-duplex conversation.
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_SEND_DATA_NOT_SEND_STATE
The local TP issued the [MC_]SEND_DATA verb, but the conversation was not in Send or Send_Pending
state.
AP_SEND_DATA_CONFIRM_SYNC_NONE
The local TP issued the [MC_]SEND_DATA verb with the type parameter set to
AP_SEND_DATA_CONFIRM, but the synchronization level of the conversation was AP_NONE. The
CONFIRM function is only valid if the synchronization level is AP_CONFIRM_SYNC_LEVEL.
AP_SEND_DATA_NOT_LL_BDY
221