Requesting confirmation

The CONFIRM option of the SEND command flushes the conversation send buffer; that is, it causes a transmission to occur. When the conversation is in send state (state 2), you can send data with the SEND CONFIRM command. You can also specify either the INVITE or the LAST option.

The send state (state 2) column of the state table for APPC mapped conversations at sync level 1 (see State tables for APPC mapped conversations at sync level 1 ) shows what happens for the possible combinations of the CONFIRM, INVITE, and LAST options. After a SEND CONFIRM command, without the INVITE or LAST options, the conversation remains in send state (state 2). If the INVITE option is used, the conversation switches to receive state (state 5). If the LAST option is used, the conversation switches to free state (state 12).

A similar effect to SEND LAST CONFIRM can by achieved by using the command sequence:
 SEND LAST
SEND CONFIRM

Note from the state tables that the SEND LAST puts the conversation into pendfree state (state 4), so data cannot be sent with a SEND CONFIRM command used in this way.

The form of command used depends on how the conversation is to continue if the required confirmation is received. However, the response from SEND CONFIRM must always be checked. See Checking the response to SEND CONFIRM.



dfhp6c0032.html | Timestamp icon Last updated: Monday, 5 June 2017