Passing conversations
Besides using FEPI START to have a task for receiving data, any program or handler can explicitly give up ownership of its conversations so that another task can use them.
You do this with the FEPI FREE command and the PASS option. Any task can then get ownership by using FEPI ALLOCATE with PASSCONVID and, if it maintains the command sequence, continue the conversation (for example, if the first task has issued a FEPI SEND with INVITE, the second task would have to issue a FEPI RECEIVE or, perhaps, a FEPI START). It is up to the two tasks to communicate between themselves, using the standard CICS methods (TS queue, COMMAREA, and so on), about the state of the conversation and its ID. FEPI does not offer any application programming facilities for this except that the new task can use FEPI EXTRACT CONV to determine details such as the data format.
If you do not employ a method of passing and saving the conversation across invocations of a pseudoconversational front-end transaction, and instead issue the default FREE command, you lose your connection to the back-end transaction, making it possible for another program to start a conversation and effectively “break into” the active transaction. This can cause the back-end application to abnormally end.
The only other method that can be used to ensure a unique relationship between front-end and back-end transactions, is to have FEPI pools containing a single FEPI node for each user. This ensures that you always get connected to the back-end transaction on the same terminal (FEPI node) to continue your conversation. However, this method can cause administrative problems where there are a large number of users.