Shutdown

A normal CICS shutdown waits for currently active tasks to end, but does not allow new tasks to start. FEPI allows existing conversations to continue within a task but does not allow them to be passed to another task (because that task would never be started), nor does it allow new conversations to be started.

Conversations that are “unowned” are ended immediately, because the tasks that would subsequently handle them would never be started. Therefore, FEPI START or FREE PASS commands issued during shutdown fail (RESP2=214); in this case the error-handling routine, after doing whatever housekeeping is required, should issue FEPI FREE to end the conversation. FEPI ALLOCATE commands issued during shutdown fail with RESP2=12.

You might need to take special action on the back-end system, for example, signing off, when the front-end application is going to shut down. For this reason, when conversations end during shutdown, the end-session handler is invoked with SHUTDOWN indicated in the EVENTVALUE field of the start data, so that the back-end system can be restored to a known state before FEPI ends; the FEPI FREE issued by the handler is treated as if RELEASE is specified. If you require this function, make sure the end-session handler is defined in the transaction list table (XLT), so that it can be started, and so that it does not adversely affect the performance of CICS shutdown. Using an end-session handler is the only way to perform special processing on shutdown, because no notification of shutdown is given to normal active transactions and conversations.

An immediate CICS shutdown ends all conversations immediately, and commands in progress fail. No further FEPI commands can be issued, and no end-session handlers are started.



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