Reset State

A TP calls the TPStarted intrinsic to gain access to LU 6.2 API. Once TPStarted has executed successfully, the TP is in Reset state.

Reset state is the only state associated with the entire TP. The remainder of the states are associated with individual conversations. From Reset state, a TP can call either MCAllocate or MCGetAllocate to allocate a conversation with a remote TP.

When the local TP calls MCAllocate, two things occur: 1) the local side of a conversation is established and placed in Send state; 2) a request is sent to the remote TP to start a conversation.

The local TP calls MCGetAllocate when it receives a request from a remote TP to start a conversation. When a conversation is requested by the remote TP, the local side of the conversation begins in Receive state.

On MPE V, a single TP can allocate up to 8 conversations, but it can call MCGetAllocate only once, so only one of its conversations can be initiated by the remote TP; the local TP must allocate the rest of its conversations by calling the MCAllocate intrinsic. On MPE XL, a single TP can allocate up to 256 conversations, and any number of these can be initiated by the remote TP.

Table 4-2 “Reset State Intrinsics” lists the intrinsics that can be called from Reset state. It also indicates what state the local side of the conversation is in after each intrinsic executes successfully. See Chapter 5 “ Intrinsic Descriptions” for more information on intrinsics.