FEPI FREE ends a task’s use and ownership of a conversation. The conversation may be ended completely, or may be passed to another task. The action depends on the processing state of the conversation:
FEPI FREE .-HOLD----. >>-FEPI FREE--CONVID(data-value)--+---------+------------------>< +-RELEASE-+ +-FORCE---+ '-PASS----'
For the access program and the unsolicited-data handler, HOLD instructs FEPI to end the conversation and to retain the session for use by another conversation. However, this is subject to any end-session processing.
For the begin-session handler and the STSN handler, HOLD tells FEPI that begin-session or STSN processing has ended, and that the conversation is ready for the next processing state.
For the end-session handler, HOLD tells FEPI that end-session processing has ended, and instructs FEPI to end the conversation and to retain the session for use by another conversation. (If CICS shutdown is in progress, HOLD is the same as RELEASE.)
For the access program and the unsolicited-data handler, RELEASE instructs FEPI to end the conversation, and to release and unbind the session that it was using, thereby forcing a new session to be started next time the connection is used. However, this is subject to any end-session processing.
For the begin-session handler and the STSN handler, RELEASE tells FEPI that begin-session or STSN processing has ended, and instructs FEPI to end the conversation without proceeding to the next processing state, and to release and unbind the session that it was using, thereby forcing a new session to be started next time the connection is used. However, this is subject to any end-session processing.
For the end-session handler, RELEASE tells FEPI that end-session processing has ended, and instructs FEPI to end the conversation, and to release and unbind the session that it was using, thereby forcing a new session to be started next time the connection is used.
Note that, under normal circumstances, after a FEPI FREE RELEASE command has been issued the session does not remain in RELEASED state, because FEPI automatically tries to reacquire the session. However, if a FEPI SET CONNECTION ACQSTATUS(RELEASED) command is issued before the FREE RELEASE, the session remains in RELEASED state.
The INVREQ condition can have the following RESP2 values: