Requesting confirmation

The CONFIRM option on the GDS SEND command flushes the conversation send buffer; that is, it causes a real transmission to occur.

Data can be sent with the GDS SEND CONFIRM command. Either the INVITE or the LAST option can also be specified.

The send state (state 2) column of the state table for APPC basic conversations at sync level 1 (see State tables for APPC basic conversations at sync level 1 ) shows what happens for the possible combinations of the CONFIRM, INVITE, and LAST options. After a GDS 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 GDS SEND LAST CONFIRM can by achieved by using the command sequence:
 GDS SEND LAST
GDS SEND CONFIRM

Note from the state tables that the GDS SEND LAST puts the conversation into pendfree state (state 4), so data cannot be sent with a GDS 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. Whichever is used, the response from GDS SEND CONFIRM must always be checked. (See Checking the response to GDS SEND CONFIRM .)



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