HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_ALLOCATE and ALLOCATE
unsigned short pip_dlen;
unsigned char far *pip_dptr;
unsigned char reserv7;
unsigned char fqplu_name[17];
unsigned char reserv8[8];
} ALLOCATE;
4.2.5 Supplied Parameters
The TP supplies the following parameters to APPC:
opcode
Possible values are:
AP_M_ALLOCATE
For the MC_ALLOCATE verb.
AP_B_ALLOCATE
For the ALLOCATE verb.
opext
Possible values are:
AP_MAPPED_CONVERSATION
For the MC_ALLOCATE verb.
AP_BASIC_CONVERSATION
For the ALLOCATE verb.
If the verb is being issued as a non-blocking verb, combine the value above (using a logical OR) with the
value AP_NON_BLOCKING.
tp_id
Identifier for the local TP.
The value of this parameter was returned by the TP_STARTED verb for an invoking TP, or by the
RECEIVE_ALLOCATE verb for an invoked TP.
conv_type
Type of conversation to allocate. This parameter is used only by the ALLOCATE verb.
Possible values are:
AP_BASIC_CONVERSATION
AP_MAPPED_CONVERSATION
If the ALLOCATE verb establishes a mapped conversation, the local TP must issue basic-conversation verbs
and provide its own mapping layer to convert data records to logical records and logical records to data records.
The partner TP can issue basic-conversation verbs and provide the mapping layer, or it can use mapped-
conversation verbs (if the implementation of APPC the partner TP is using supports mapped-conversation
verbs). For further information, refer to the IBM publication Systems Network Architecture Format and
Protocol Reference Manual: Architecture Logic for LU Type 6.2.
sync_level
Synchronization level of the conversation.
110