Ending Conversations

When your TP has finished communicating with its partner, deallocate the conversation by calling the Deallocate service, or the Send_Data service with a send_type of send_and_deallocate. On the deallocate_type parameter of the Deallocate service, specify one of the following:

Deallocate_sync_level

Deallocates based on the sync_level set by the allocate function:

If sync_level is none (no confirmation), performs the function of the flush service and deallocates the conversation normally
If sync_level is confirm, requests a confirmation; if granted, deallocates the conversation normally.
If sync_level is syncpt, defers the deallocation until the program issues a Commit call. Upon successful completion of the Commit call, the system deallocates the conversation.

Deallocate_flush

Performs the function of the flush service, and deallocates the conversation normally.

Deallocate_confirm

Requests a confirmation:

If granted (Confirmed), deallocates the conversation normally
If rejected by Send_Error, the conversation continues.

Deallocate_abend

Performs the function of the flush service and deallocates the conversation abnormally.

For more information about the deallocate types, see the explanations for return codes 17 and 18 under Explanations of Return Codes for CPI Communications Services. The partner is notified of the deallocate request by status_received parameter or by return code.

As a result of the deallocate function, both partners go into Reset state and the conversation ends.