Recovery and restart on z/OS

Recovery and restart on z/OS

Use the links in this topic to find out about the features of IBM MQ for z/OS® for restart and recovery.

IBM MQ for z/OS has robust features for restart and recovery. For information about how a queue manager recovers after it has stopped, and what happens when it is restarted, see the following subtopics:

How changes are made to data in IBM MQ for z/OS
IBM MQ for z/OS must interact with other subsystems to keep all the data consistent. This topic contains information about units of recovery, what they are and how they are used in back outs.
How consistency is maintained in IBM MQ for z/OS
Data in IBM MQ for z/OS must be consistent with batch, CICS®, IMS, or TSO. Any data changed in one must be matched by a change in the other.
What happens during termination in IBM MQ for z/OS
A queue manager terminates normally in response to the STOP QMGR command. If a queue manager stops for any other reason, the termination is abnormal.
What happens during restart and recovery in IBM MQ for z/OS
IBM MQ uses its recovery log and the bootstrap data set (BSDS) to determine what to recover when it restarts. The BSDS identifies the active and archive log data sets, and the location of the most recent IBM MQ checkpoint in the log.
How in-doubt units of recovery are resolved
If IBM MQ loses its connection to another resource manager, it typically attempts to recover all inconsistent objects at restart.
Shared queue recovery
Use this topic to understand IBM MQ recovery and resilience of various components in the queue sharing group environment.
Parent topic: IBM MQ for z/OS concepts

Related information

Plan for backup and recovery
IBM MQ for z/OS recovery actions
Administer z/OS
Messages for IBM MQ for z/OS
MQSC reference