HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_SEND_ERROR and SEND_ERROR
4.16.9 Waiting for Partner TP
The [MC_]SEND_DATA verb may wait indefinitely because the partner TP has not issued a receive verb. This is
because the send buffer may fill up and APPC cannot transmit its contents to the partner LU because the partner
LU has no buffers to receive the data.
4.16.10 Logical Records in Basic Conversations
When using the basic-conversation SEND_DATA verb, the application must supply data in the form of logical
records (with an LLID field at the start of each data record). For more information, see Section 2.11.1,
Logical
Records.
UNIX
In a conversation with a synchronization level of AP_SYNCPT, the data to be sent may be in PS Header format;
this is indicated by a length field of 0x0001. The Syncpoint Manager is responsible for setting up the appropriate
PS headers based on the Syncpoint functions required by the application.
4.17 MC_SEND_ERROR and SEND_ERROR
The MC_SEND_ERROR or SEND_ERROR verb notifies the partner TP that the local TP has encountered an
application-level error.
The local TP sends the error notification immediately to the partner TP; it does not hold the information in the local
LU’s send buffer.
For a half-duplex conversation, after successful execution of this verb, the conversation is in Send state for the local
TP and in Receive state for the partner TP. For a full-duplex conversation, there is no state change after successful
execution of this verb.
4.17.1 VCB Structure: MC_SEND_ERROR
UNIX
The definition of the VCB structure for the MC_SEND_ERROR verb is as follows:
typedef struct mc_send_error
{
AP_UINT16 opcode;
unsigned char opext;
unsigned char format; /* Reserved */
AP_UINT16 primary_rc;
AP_UINT32 secondary_rc;
unsigned char tp_id[8];
AP_UINT32 conv_id;
unsigned char rts_rcvd;
unsigned char err_type;
unsigned char err_dir;
unsigned char expd_rcvd;
unsigned char reserv5[2];
unsigned char reserv6[4];
} MC_SEND_ERROR;
224