HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Control Verbs

RECEIVE_ALLOCATE

This parameter determines whether the TPs can request conﬁrmation of receipt of data and conﬁrm receipt

of data. Possible values are:

AP_CONFIRM_SYNC_LEVEL

The partner TPs can use conﬁrmation processing in this conversation.

AP_SYNCPT

The TPs can use LU 6.2 Syncpoint functions in this conversation. For more information, see Section

1.12,

Syncpoint Support.

AP_NONE

Conﬁrmation processing is not used in this conversation.

conv_type

Type of conversation chosen by the partner TP, using the [MC_]ALLOCATE verb. Possible values are:

AP_BASIC_CONVERSATION

AP_MAPPED_CONVERSATION

user_id

If the partner TP set [MC_]ALLOCATE’s security parameter to

AP_PGM or AP_SAME, this parameter contains

the user ID sent from the partner TP. The user ID is a type-AE EBCDIC character string, padded on the

right with EBCDIC spaces to 10 characters if necessary. If the partner TP set [MC_]ALLOCATE’s security

parameter to AP_NONE, this parameter is set to 10 EBCDIC blanks.

lu_alias

Alias by which the local LU is known to the local TP. This is an ASCII character string.

plu_alias

Alias by which the partner LU (from which the incoming Allocate was received) is known to the local TP.

This is an ASCII character string.

mode_name

Mode name speciﬁed by the [MC_]ALLOCATE verb in partner TP. This is the name of a set of networking

characteristics deﬁned during conﬁguration. This name is a type-A EBCDIC character string.

conv_group_id

The conversation group identiﬁer of the session that the new conversation uses.

fqplu_name

Fully qualiﬁed name of the partner LU.

This parameter contains the network name, an EBCDIC period, and the partner LU name. Each of the two

names is an 8-byte EBCDIC character string, which can consist of characters from the type-A EBCDIC

character set as follows:

• Uppercase letters

• Numerals 0–9

• Special characters $, #, and @

UNIX

pip_incoming

Speciﬁes whether the partner TP supplied program initialization parameter (PIP) data on the

[MC_]ALLOCATE request. Possible values are:

AP_YES

The partner TP supplied PIP data. The local TP should issue one of the [MC_]RECEIVE verbs to

receive the data; the ﬁrst data record received will be the PIP data.