Using Advanced Program-to-Program Communication › Conversation Deallocation

Previous Topic: Error Processing

Next Topic: Sample Conversations

Conversation Deallocation

Regardless of which end started a conversation, any procedure can terminate it from send state by issuing one of the deallocate requests:

&APPC DEALLOCATE
&APPC DEALLOCATE TYPE=FLUSH
&APPC DEALLOCATE TYPE=CONFIRM
&APPC DEALLOCATE TYPE=ABEND

If no type is specified, then it will default to FLUSH if the conversation has a sync_level of NONE, or CONFIRM if the conversation has a sync_level of CONFIRM (as set by the allocation request and reflected in the &ZAPPCSYN system variable).

A TYPE=CONFIRM deallocation is conditional upon the remote procedure issuing an CONFIRMED response. The only other valid response is a SEND_ERROR, which means the conversation remains active and the error sender is placed in send state. If &RETCODE of 0 is returned the deallocation was successful.

A TYPE=FLUSH or TYPE=ABEND is unconditional as long as the request is accepted. A &RETCODE of 0 indicates that the conversation is terminated.