Recovery and restart on z/OS

Use this topic to understand the recovery and restart mechanisms used by IBM MQ .

• Restarting IBM MQ
  After a queue manager terminates there are different restart procedures needed depending on how the queue manager terminated. Use this topic to understand the different restart procedures that we can use.
• Alternative site recovery on z/OS
  We can recover a single queue manager or a queue sharing group, or consider disk mirroring.
• Reinitializing a queue manager
  If the queue manager has terminated abnormally you might not be able to restart it. This could be because your page sets or logs have been lost, truncated, or corrupted. If this has happened, you might have to reinitialize the queue manager (perform a cold start).
• Use the z/OS Automatic Restart Manager (ARM)
  Use this topic to understand how we can use ARM to automatically restart your queue managers.
• Recovering units of work manually
  We can manually recover units of work CICS, IMS, RRS, or other queue managers in a queue sharing group. We can use queue manager commands to display the status of the units of work associated with each connection to the queue manager.

Parent topic: Administer IBM MQ for z/OS