HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_RECEIVE_EXPEDITED_DATA and RECEIVE_EXPEDITED_DATA
primary_rc
New state
AP_DEALLOC_ABEND
AP_DEALLOC_ABEND_PROG
AP_DEALLOC_ABEND_SVC
AP_DEALLOC_ABEND_TIMER
AP_DEALLOC_NORMAL
Reset (half-duplex conversation) or Send_Only
(full-duplex conversation)
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.12.9 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 (see Section 2.11.1, Logical Records for more information). The Syncpoint
Manager is responsible for converting the data into the appropriate Syncpoint commands.
4.13 MC_RECEIVE_EXPEDITED_DATA and
RECEIVE_EXPEDITED_DATA
The MC_RECEIVE_EXPEDITED_DATA or RECEIVE_EXPEDITED_DATA verb receives any expedited data that
is currently available from the partner TP. If no data is currently available, the verb can either return immediately
or wait for data to arrive.
4.13.1 VCB Structure: MC_RECEIVE_EXPEDITED_DATA
The definition of the VCB structure for the MC_RECEIVE_EXPEDITED_DATA verb is as follows:
typedef struct mc_receive_expedited_data
{
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 rtn_ctl;
unsigned char reserv1[3];
unsigned char rts_rcvd;
unsigned char expd_rcvd;
AP_UINT16 max_len;
AP_UINT16 dlen;
unsigned char *dptr;
} MC_RECEIVE_EXPEDITED_DATA;
195