What happens when the CICS-WebSphere MQ connection shuts down
The connection between CICS® and WebSphere® MQ has two types of shutdown, quiesced (or orderly) shutdown and forced shutdown. Connection shutdown can result from an operator action, from a shutdown of CICS, or from the WebSphere MQ queue manager.
Table 1 summarizes how the adapter handles different forms of connection shutdown when the connection is active. If CICS or WebSphere MQ shuts down when the connection is not active (for example, after it has been quiesced), no action is taken and no messages are issued.
| Method of shutdown | How this is handled by the adapter |
|---|---|
| Quiesced shutdown of connection (EXEC CICS SET MQCONN NOTCONNECTED BUSY(WAIT|NOWAIT), CEMT SET MQCONN NOTCONNECTED, or CKQC STOP) | Mark the status of the adapter as Quiescing. Allow both active and waiting tasks to complete. Allow sync point. Do not allow calls from a new task. The last task initiates disconnection from WebSphere MQ. |
| Forced shutdown of connection (EXEC CICS SET MQCONN NOTCONNECTED BUSY(FORCE), CEMT SET MQCONN FORCENOTCON, or CKQC STOP FORCE) | Mark the status of the adapter as StoppingForce. Disconnect from WebSphere MQ. First resume tasks waiting in WebSphere MQ, including instances of CKTI, then forcepurge any inflight tasks that accessed WebSphere MQ. |
| CICS warm shutdown | Issue message DFHMQ0411 I. Initiate a quiesced shutdown of the connection. |
| CICS immediate shutdown | Issue message DFHMQ0410 I. Any inflight tasks using WebSphere MQ are backed out. |
| CICS abend | Issue message DFHMQ0412 I. |
| WebSphere MQ quiesced | Initiate a quiesced shutdown of the connection. |
| WebSphere MQ abend or forced shutdown | Initiate a forced shutdown of connection. |