Conversational applications

In the simplest case, an access program starts a conversation with a FEPI ALLOCATE command specifying the pool of connections that is to be used.

The command returns an identifier, the conversation ID, that is used to refer to the conversation subsequently. The program then issues a series of FEPI SEND, RECEIVE (and possibly other) commands for the conversation, each specifying the identifier, so that FEPI knows which conversation—and therefore which connection and target —the command is for. Finally, it ends the conversation with a FEPI FREE command. If it does not, the conversation is ended by FEPI when the task ends.

The FEPI FREE command should normally specify the HOLD option, so that the connection remains ready for use by another conversation. If the RELEASE option is used, or you leave the conversation to be freed by FEPI at the end of task, the session is ended, and a new one must be started for the next conversation; this is inefficient and, therefore, not recommended.



dfhp7c00176.html | Timestamp icon Last updated: Monday, 5 June 2017