Normal termination of a conversation

The SEND LAST command is used to terminate a conversation. It should be used in conjunction with either the WAIT or CONFIRM options, the SYNCPOINT command, or the WAIT CONVID command (depending on the conversation sync level).

Table 1. Command sequences for ending a conversation
Sync level Command sequence
0

SEND LAST WAIT
FREE

1

SEND LAST CONFIRM
FREE

2

SEND LAST
SYNCPOINT
FREE

It is important that the SEND LAST command for sync level 2 is not accompanied by WAIT or CONFIRM because either of these options will cause the conversation to end before the subsequent syncpoint has propagated to the partner transaction. This may mean that protected resources of one transaction could be committed while those in the partner transaction could be backed out. The resulting state errors may also lead to the session being unbound.

From the state tables it can be seen that it is possible to end a conversation by issuing the FREE command, provided the conversation is in send state (state 2). This will generate an implicit SEND LAST WAIT command before the FREE is executed and is therefore not recommended for conversations using sync levels 1 and 2.

Note: A distributed transaction should not end a conversation by issuing an EXEC CICS® RETURN command, but instead follow the sequence of commands shown in Table 1. The issue of an EXEC CICS RETURN could lead to one or both transactions ending abnormally.


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