What happens when you stop a queue manager

When a queue manager stops normally, WebSphere® MQ stops all activity in an orderly way. You can stop WebSphere MQ by using either quiesce, force, or restart mode.

The effects are given in Table 1.

Table 1. Stopping a queue manager in QUIESCE, FORCE, and RESTART mode
Thread type QUIESCE FORCE RESTART
Active threads Run to completion Back out Back out
New threads Can start Not permitted Not permitted
New connections Not permitted Not permitted Not permitted

With CICS®, a current thread runs only to the end of the unit of work. With CICS, stopping a queue manager in quiesce mode stops the CICS-WebSphere MQ adapter, and so, if an active task contains more than one unit of work, the task does not necessarily run to completion.

When you stop a queue manager, in any mode, the steps are as follows:
  1. Connections are ended.
  2. WebSphere MQ ceases to accept commands.
  3. WebSphere MQ ensures that any outstanding updates to the page sets are completed.
  4. The DISPLAY USAGE command is issued internally by WebSphere MQ so that the restart relative byte address (RBA) is recorded on the z/OS® console log.
  5. The shutdown checkpoint is taken and the WebSphere MQ bootstrap data set (BSDS) is updated.

If you stop a queue manager in force or restart mode, no new threads are allocated, and work on connected threads is rolled back. Using these modes can create indoubt units of work for threads that are between commit processing phases. They are resolved when WebSphere MQ is reconnected with the controlling CICS, IMS™, or RRS subsystem.

Quiesce mode does not affect indoubt units of work. Any unit of work that is indoubt remains indoubt.



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