Migrating to V6

The new functions for this release are described in the WebSphere MQ for z/OS Concepts and Planning Guide. Consider which of these functions you want to use before customizing WebSphere MQ because you might not need to perform all the migration tasks.

When you migrate from a previous version of WebSphere MQ for z/OS or MQSeries for OS/390, we can continue to use your existing queue managers with the new version, including their page sets, log data sets, object definitions, and initialization input data sets. We can continue to use your existing queues, including system queues such as the SYSTEM.CHANNEL.SYNCQ. You should not cold start your queue managers when migrating from a previous version because you do not need to. If you do, you will lose all your messages and other information such as channel state.

However, there are some tasks that we need to perform when migrating from a previous version. Whether we need to perform each task depends on which of the new features you want to use, and which level of WebSphere MQ you are migrating from. Generally, the earlier the version of WebSphere MQ you are migrating from, the more tasks we need to perform.

If you use the Client Attachment feature, install and use the V6 feature. Previous versions of this feature will not work with WebSphere MQ V6.0.

If you are using CICS, restart the CICS region after the migration to ensure that you use the new versions of any changed files. Likewise, if you are using IMS (other than the WebSphere MQ IMS bridge), restart the IMS control region after the migration.