HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Control Verbs

RECEIVE_ALLOCATE

3.3.2 VCB Structure: RECEIVE_ALLOCATE (Windows)

WINDOWS

The deﬁnition of the VCB structure for the RECEIVE_ALLOCATE verb is as follows:

typedef struct receive_allocate

{

unsigned short opcode;

unsigned char opext;

unsigned char reserv2;

unsigned short primary_rc;

unsigned long secondary_rc;

unsigned char tp_name[64];

unsigned char tp_id[8];

unsigned long conv_id;

unsigned char sync_level;

unsigned char conv_type;

unsigned char user_id[10];

unsigned char lu_alias[8];

unsigned char plu_alias[8];

unsigned char mode_name[8];

unsigned char reserv3[2];

unsigned long conv_group_id;

unsigned char fqplu_name[17];

unsigned char reserv4[5];

} RECEIVE_ALLOCATE;

3.3.3 Supplied Parameters

The TP supplies the following parameters to APPC:

opcode

AP_RECEIVE_ALLOCATE (standard form)

UNIX

AP_RECEIVE_ALLOCATE_EX (extended form)

tp_name

Name of the local TP. APPC matches this name with the TP name speciﬁed in the incoming Attach, which

is generated by the [MC_]ALLOCATE verb in the invoking TP. If the TP is to be automatically started by

SNAplus2, this TP name must match a TP name speciﬁed in the invokable TP data ﬁle.

This parameter is a 64-byte case-sensitive EBCDIC character string. The

tp_name parameter normally consists

of characters from the type-AE EBCDIC character set. These characters are as follows:

• Uppercase and lowercase letters

• Numerals 0–9

• Special characters $, #, @, and period (.)

If the TP name is fewer than 64 bytes, use EBCDIC blanks (0x40) to pad it on the right.

The SNA convention for naming a service TP is an exception to the above; the name consists of up to 4

characters, of which the ﬁrst character is a hexadecimal byte between 0x00 and 0x3F. The other characters

are from the EBCDIC AE character set.