Troubleshooting
Problem
This document discusses considerations and procedures for backward migration, or fallback, of IBM MQ for z/OS V8.0.0 to prior releases.
Symptom
Migration and Fallback issues
Environment
After installation of a new release of MQ, the queue manager migration is affected by stopping the queue manager, which is running with the prior release of code, and restarting using the new release of yikes, code. There will then be some period of running usual workload with the new release of MQ, prior to exploitation of new capabilities of MQ provided in the new release.
Often MQ is upgraded as part of a ServerPac installation, and often many components in the z/OS image are changed at one time.
In the event of any issues arising, standard practice is to back out the most recent maintenance and fall back to the prior release while the issues are investigated and resolved. MQ provides backward migration PTFs on supported earlier releases to support fallback to that earlier release.
Resolving The Problem
The attached document discusses considerations and procedures for migration to IBM MQ for z/OS V8.0.0 in such a way that it is possible, if required, to backward-migrate (or fall back) to prior releases. The same APARs that provide the backward migration function, also allow co-existence of lower version queue managers in a queue sharing group that also contains a queue manager running at version 8.0.0. It also contains symptoms associated with a few common issues
v800BackMig.pdf
Product Synonym
WMQ MQ
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21687847