HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_TEST_RTS and TEST_RTS
AP_UNSUCCESSFUL
REQUEST_TO_SEND notification has not been received.
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 specific 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:
AP_BAD_CONV_ID
The value of conv_id did not match a conversation identifier assigned by APPC.
AP_BAD_TP_ID
The value of tp_id did not match a TP identifier assigned by APPC.
UNIX
AP_INVALID_FORMAT
The reserved field format was set to a nonzero value.
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.
AP_TEST_INVALID_FOR_FDX
The local TP attempted to use the [MC_]TEST_RTS verb in a full-duplex conversation. This verb can
be used only in a half-duplex conversation.
State Check
No state check errors occur for this verb.
Other Conditions
If the verb does not execute because other conditions exist, APPC returns primary return codes (and, if applicable,
secondary return codes). For information about these return codes, see Appendix B, Common Return Codes.
Possible return codes are:
primary_rc
AP_COMM_SUBSYSTEM_ABENDED
AP_CONVERSATION_TYPE_MIXED
AP_INVALID_VERB
AP_TP_BUSY
AP_UNEXPECTED_SYSTEM_ERROR
WINDOWS
AP_COMM_SUBSYSTEM_NOT_LOADED
AP_STACK_TOO_SMALL
AP_INVALID_VERB_SEGMENT
241