Recovery and restart

Restarting WebSphere MQ
Restarting after a normal shutdown
Restarting after an abnormal termination
Restarting if you have lost your page sets
Restarting if you have lost your log data sets
Restarting if you have lost your CF structures
Recovering a single queue manager at an alternative site
Fast copy techniques
Recovering a queue-sharing group
CF structure media recovery
Backing up the queue-sharing group at the prime site
Recovering a queue-sharing group at the alternative site
Reinitializing a queue manager
Reinitializing a queue manager that is not in a queue-sharing group
Reinitializing queue managers in a queue-sharing group
Using the z/OS Automatic Restart Manager (ARM)
What is the ARM?
ARM couple data sets
ARM policies
Defining an ARM policy
Activating an ARM policy
Registering with ARM
Using ARM in a WebSphere MQ network
Restarting on a different z/OS image with LU 6.2
Restarting on a different z/OS image with TCP/IP
When using clustering
When connecting to a queue-sharing group
Recovering units of work manually
Displaying connections and threads
Active units of work
Unresolved units of work
Recovering CICS units of recovery manually
What happens when the CICS adapter restarts
How to resolve CICS units of recovery manually
Recovering IMS units of recovery manually
What happens when the IMS adapter restarts
How to resolve IMS units of recovery manually
Recovery procedure
Recovering RRS units of recovery manually
Recovering units of recovery on another queue manager in the queue-sharing group
Example recovery scenarios
Shared queue problems
Queue is both private and shared
Active log problems
Dual logging is lost
Active log stopped
One or both copies of the active log data set are damaged
Write I/O errors on an active log data set
I/O errors occur while reading the active log
Replacing the data set
Active log is becoming full
Active log is full
Archive log problems
Allocation problems
Off-load task terminated abnormally
Insufficient DASD space to complete off-load processing
Read I/O errors on the archive data set while WebSphere MQ is restarting
BSDS problems
Error occurs while opening the BSDS
Log content does not agree with the BSDS information
Both copies of the BSDS are damaged
Unequal time stamps
Out of synchronization
I/O error
Page set problems
Page set I/O errors
Page set full
Coupling Facility and DB2 problems
Storage medium full
A DB2 system fails
A DB2 data-sharing group fails
DB2 and the Coupling Facility fail
Problems with long-running units of work
Old unit of work found during restart
IMS-related problems
IMS cannot connect to WebSphere MQ
IMS application problem
IMS is not operational
Hardware problems