HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Control Verbs

GET_TP_PROPERTIES

unsigned short opcode;

unsigned char reserv2[2];

unsigned short primary_rc;

unsigned long secondary_rc;

unsigned char tp_id[8];

unsigned char tp_name[64];

unsigned char lu_alias[8];

unsigned char luw_id[26];

unsigned char fqlu_name[17];

unsigned char reserv3[10];

unsigned char user_id[10];

} GET_TP_PROPERTIES;

3.5.3 Supplied Parameters

The TP supplies the following parameters to APPC:

opcode

AP_GET_TP_PROPERTIES

tp_id

Identiﬁer for the local TP.

The value of this parameter is returned by the TP_STARTED verb in the invoking TP or by RE-

CEIVE_ALLOCATE in the invoked TP.

3.5.4 Returned Parameters

After the verb executes, APPC returns parameters to indicate whether the execution was successful and, if not, to

indicate the reason the execution was not successful.

Successful Execution

If the verb executes successfully, APPC returns the following parameters:

primary_rc

AP_OK

tp_name

TP name of the local TP, as speciﬁed on the TP_STARTED or RECEIVE_ALLOCATE verb. This is a 64-byte

EBCDIC character string.

lu_alias

Alias by which the local LU is known to the local TP, as speciﬁed on the TP_STARTED or RE-

CEIVE_ALLOCATE verb. This is an 8-byte ASCII character string.

UNIX

luw_id

The unprotected Logical Unit of Work Identiﬁer (LUWID) for the transaction in which the TP is participating.

The LUWID is assigned on behalf of the TP that initiates the transaction, and enables you to correlate

the different conversations that make up the transaction. The unprotected LUWID is used to correlate

unprotected conversations (those with a sync_level of AP_NONE or AP_CONFIRM_SYNC_LEVEL); for TPs

that use Syncpoint processing, there is an additional protected LUWID for conversations with a sync_level of

AP_SYNCPT (for more information, see ).