You can shut down a connection between WebSphere MQ and the CICS(R) adapter by using the CKQC transaction or an application program. There are two types of shutdown:
Other forms of connection shutdown result from a termination of CICS or the queue manager. Table 3 summarizes how the adapter handles different forms of connection shutdown.
Method of shutdown | How this is handled by the adapter |
---|---|
CKQC STOP (A quiesced shutdown) | Mark the status of the adapter as Quiescing. Allow both active and waiting tasks to complete. Allow syncpoint. Do not allow calls from a new task. The last task initiates disconnection from WebSphere MQ. |
CKQC STOP FORCE | Mark the status of the adapter as StoppingForce. Disconnect from WebSphere MQ. Resume waiting tasks. Fail any in-flight or following MQI calls. |
CICS warm shutdown | Issue message CSQC411I. Initiate a quiesced shutdown of the connection; see CKQC STOP, above. |
CICS immediate shutdown | Issue message CSQC410I. Any in-flight tasks using WebSphere MQ are backed out. |
CICS abend | Issue message CSQC412I. |
WebSphere MQ quiesced | Initiate a quiesced shutdown of the connection; see CKQC STOP, above. |
WebSphere MQ abend or forced shutdown | Initiate a forced shutdown of connection; see CKQC STOP FORCE, above. |
Notes:
|
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq846c |