HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_TEST_RTS_AND_POST and TEST_RTS_AND_POST
Note
When this verb is issued, it returns immediately with a primary_rc which indicates whether
or not the verb was issued successfully. The only returned parameters which are valid at
this stage are primary_rc and secondary_rc (if the primary_rc is not
AP_OK). The possible
primary_rc and secondary_rc values are as described later in this section.
If this primary_rc is
AP_OK, the verb has successfully begun to wait for RE-
QUEST_TO_SEND notification. When the verb has completed (either because the
notification was received, or because it was terminated by the end of the conversation
or by an error), APPC calls the supplied callback routine. At this point, the returned
parameters are as shown below. The primary_rc and secondary_rc parameters will now
have new values indicating whether or not the REQUEST_TO_SEND notification was
received, and should be examined again.
Successful Execution
If the verb executes successfully, APPC returns the following parameter:
primary_rc
AP_OK
REQUEST_TO_SEND notification was 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.
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_INVALID_CALLBACK_HANDLE
The callback parameter was set to a null pointer, and the verb was issued using the synchronous entry
point (or using the asynchronous entry point with a null pointer to a callback routine). For more
information, see Section 4.20.9, Usage Notes.
AP_TEST_INVALID_FOR_FDX
The local TP attempted to use the [MC_]TEST_RTS_AND_POST verb in a full-duplex conversation.
This verb can be used only in a half-duplex conversation.
245