Allocating a session to the conversation

Initially, there is no conversation, and therefore no conversation state. By issuing an ALLOCATE command, the front-end transaction acquires a session to start a new conversation.

The RESP value returned should be checked to ensure that a session has been allocated. If the session is successfully allocated, DFHRESP(NORMAL), the conversation is in allocated state (state 1) and the session identifier ( convid ) in EIBRSRCE must be saved immediately.

The convid must be used in subsequent commands for this conversation. Figure 1 shows an example of an ALLOCATE command.

Note: If the remote system is using z/OS® Communications Server persistent session support, you may need to code a timeout value on the ALLOCATE command. See Effect of z/OS Communications Server persistent sessions support for DTP conversations on APPC sessions.