ARM (Automatic Restart Manager), availability, shared queues, queue-sharing groups" />
Using the z/OS Automatic Restart Manager (ARM)
We can use WebSphere MQ for z/OS in conjunction with the z/OS automatic restart manager (ARM). If a queue manager or a channel initiator has failed, ARM restarts it on the same z/OS image. If z/OS fails, a whole group of related subsystems and applications also fail. ARM can restart all the failed systems automatically, in a predefined order, on another z/OS image within the sysplex. This is called a cross-system restart.
ARM enables rapid recovery of in-doubt transactions in the shared queue environment. It also gives higher availability if you are not using queue-sharing groups.
We can use ARM to restart a queue manager on a different z/OS image within the sysplex in the event of z/OS failure.
To enable automatic restart, do the following:
- Set up an ARM coupling data set.
- Define the automatic restart actions that you want z/OS to perform in an ARM policy.
- Start the ARM policy.
If you want to restart queue managers in different z/OS images automatically, every queue manager in each z/OS image on which that queue manager might be restarted must be defined with a sysplex-wide unique 4-character subsystem name.
Using ARM with WebSphere MQ is described in the WebSphere MQ for z/OS System Administration Guide.