HP-UX SNAplus2 R7 APPC Programmer's Guide

APPC Conversation Verbs
MC_CONFIRM and CONFIRM
AP_COMM_SUBSYSTEM_ABENDED
AP_INVALID_VERB
AP_TP_BUSY
AP_UNEXPECTED_SYSTEM_ERROR
WINDOWS
AP_COMM_SUBSYSTEM_NOT_LOADED
AP_STACK_TOO_SMALL
AP_INVALID_VERB_SEGMENT
APPC does not return secondary return codes with these primary return codes.
4.2.7 State When Issued
The conversation state is Reset when the TP issues this verb. It can be issued during an existing conversation which
is in any state, since it always implies the start of a new conversation which is in Reset state.
4.2.8 State Change
Upon successful execution of this verb (primary_rc is AP_OK), the state of the new conversation is Send (for a
half-duplex conversation) or Send_Receive (for a full-duplex conversation). If the verb fails, the state remains
unchanged.
4.2.9 EBCDIC-ASCII, ASCII-EBCDIC Translation
Several parameters of the [MC_]ALLOCATE verb are EBCDIC or ASCII strings. A TP can use the Common
Service Verb CONVERT to translate a string from one character set to the other. For further information, refer to
the HP-UX SNAplus2 CSV Programmer’s Guide.
4.2.10 Immediate Allocation
To ensure that the conversation with the partner is started immediately, the invoking TP can issue the [MC_]FLUSH
or [MC_]CONFIRM verb immediately after the [MC_]ALLOCATE verb. ([MC_]CONFIRM applies to half-duplex
conversations only.) Otherwise, the [MC_]ALLOCATE request accumulates with other data in the local LU’s send
buffer until the buffer is full.
4.2.11 Confirming the Allocation (half-duplex conversation only)
By issuing the [MC_]CONFIRM verb after [MC_]ALLOCATE, the invoking TP can immediately determine whether
the allocation was successful (if sync_level is set to AP_CONFIRM_SYNC_LEVEL).
4.3 MC_CONFIRM and CONFIRM
The MC_CONFIRM or CONFIRM verb sends the contents of the local LU’s send buffer and a confirmation request
to the partner TP.
118