Allocating a session to the conversation
Initially, there is no conversation, and therefore no conversation state.
The front-end transaction acquires a session to start a new conversation by issuing an ALLOCATE command.
The RESP value should be checked to ensure that a session has been allocated. If successful, the RESP value is DFHRESP(NORMAL), the conversation is in allocated state (state 1) and the session identifier ( convid ) from EIBRSRCE must be saved immediately. The convid must be used in subsequent commands for this conversation.
If the front-end transaction is started by ATI in the local region, and is required to hold a conversation with an LUTYPE6.1 session as its principal facility, the session has already been allocated when the transaction starts. You can omit the SESSION option from commands relating to the principal facility. If, however, you want to name the session explicitly in these commands, you should obtain its name from EIBTRMID.