Stopping the CICS Transaction Gateway

There are two scenarios for shutdown, normal and immediate.

The normal shutdown scenario is the recommended method for stopping the CICS® Transaction Gateway. The immediate shutdown scenario is not recommended except in emergencies; there is no guarantee that work in progress will complete.

Normal shutdown
In a normal shutdown, the Gateway daemon waits for work in progress to complete. During this time, new work is not allowed to start. When all work has completed or all Java™ clients have disconnected, the Gateway daemon shuts down.
Immediate shutdown
Any outstanding work is terminated abruptly. Existing connections are broken; requests for new connections are refused. The Gateway daemon shuts down without waiting for XA transactions to complete. Extended LUWs and work in a pre-prepare state are rolled back.

XA transactions that are in post-prepare state are not rolled back during an immediate shutdown. If no other instance of the CICS Transaction Gateway is running under the same RRM name, it is not possible for the transaction manager (WebSphere®) to recover indoubt XA transactions until the CICS Transaction Gateway is restarted.

If TCP/IP load balancing is in use, multiple CICS Transaction Gateways are running under the same RRS name. Requests to resolve indoubt XA transactions are sent to other Gateway daemons that are still running in the same Gateway group.

You can perform an immediate shutdown if a normal shutdown is taking too long. You cannot request a normal shutdown after you have issued the command for an immediate shutdown.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//ctgzos/dfhtla8.html