HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Control Verbs

RECEIVE_ALLOCATE

AP_NO

The partner TP did not supply PIP data.

duplex_type

Duplex type of the new conversation. Possible values are:

AP_HALF_DUPLEX

AP_FULL_DUPLEX

password

If the partner TP set [MC_]ALLOCATE’s

security parameter to AP_PGM, this parameter contains the password

speciﬁed by the partner TP on the [MC_]ALLOCATE verb. The password 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 or AP_SAME, this parameter is set to 10 EBCDIC

blanks.

For security reasons, SNAplus2 does not store the password after returning it on the RECEIVE_ALLOCATE

verb. If the application needs to check this parameter, it must use the value returned on RE-

CEIVE_ALLOCATE; the password is not returned on any subsequent verbs. The application can retrieve the

user ID at any point during the conversation by issuing the GET_TP_PROPERTIES verb.

Unsuccessful Execution

If the verb does not execute successfully, APPC returns a primary return code parameter to indicate the type of

error and a secondary return code parameter to provide speciﬁc details about the reason for unsuccessful execution.

Parameter Check

If the verb does not execute because of a parameter error, APPC returns the following parameters:

primary_rc

AP_PARAMETER_CHECK

secondary_rc

Possible values are:

UNIX

AP_BAD_DLOAD_ID

The value speciﬁed for the dload_id parameter was not recognized.

AP_INVALID_FORMAT

The format byte was set to a value that was not valid.

AP_INVALID_LU_ALIAS

The lu_alias parameter contained a character that was not valid. (This value is returned for the extended

form of RECEIVE_ALLOCATE, not for the standard form.)

UNIX

AP_SYNC_NOT_ALLOWED

The application issued this verb within a callback routine, using the synchronous APPC entry point.

Any verb issued from a callback routine must use the asynchronous entry point.