Upgrading to WebSphere MQ for z/OS Version 7.0
===============================================
This section describes the things that you must consider if you are migrating a single queue manager from a previous version of WebSphere® MQ.
First class migration support is provided to WebSphere MQ for z/OS® Version 7.0 from WebSphere MQ for z/OS Version 6.0. This means you can restart a queue manager at WebSphere MQ Version 7.0 by replacing the executable code (for example, the STEPLIB data sets) with equivalent Version 7.0 libraries and then restarting the queue manager. When a backward migration PTF has been applied to Version 6.0 code, it is possible to fall back from Version 7.0 operation to Version 6.0.
Start of changeThe points below can be carried out before or after the initial stage (1) of migrating a single queue manager from a previous version of WebSphere MQ.
* Apply the Version 7.0 coexistence and backward migration PTFs to the Version 6.0 code.
* Restart production WebSphere MQ systems with this PTF-updated Version 6.0 code. Verify correct function before proceeding and review any special actions detailed in the PTFs. If you require fall back at this stage, use normal maintenance procedures to revert to the Version 6.0 code before PTF application.
End of change
Follow these steps to migrate a production queue manager from WebSphere MQ Version for z/OS Version 6.0 to WebSphere MQ Version for z/OS Version 7.0:
1. Install Version 7.0 early code. Refresh the early code level of all queue managers in the LPAR.
2. Restart production WebSphere MQ systems with Version 7.0 code. Verify correct function of existing applications before using any new Version 7.0 functions. If problems become apparent at this stage, fall back to the Version 6.0 code with backward migration PTFs that have been previously validated for your environment.
For a queue-sharing group, apply the Version 6.0 coexistence and backward migration PTFs to all members before you migrate any member to Version 7.0.
For releases earlier than Version 6.0, no backward migration support from Version 7.0 is provided. You can migrate a queue manager from a release earlier than Version 6.0 directly to Version 7.0, but if problems arise there is no good fall back capability. This is not good practice for production systems, but it might be sufficient for a test queue manager. See section Migrating from an earlier unsupported release of WebSphere MQ or MQSeries for further information. Ensure that production systems are fully migrated to Version 6.0 and stability is achieved before migration to Version 7.0.
* Migrating to WebSphere MQ for z/OS Version 7.0
You might need to perform some additional tasks when migrating from a previous version, depending 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 you need to perform.
* Migrating from Version 6.0
* Start of changeControlling new functionality and backward migration using the OPMODE propertyEnd of change
The availability of new functions and backward migration for WebSphere MQ for z/OS can be controlled using the OPMODE property in the CSQ6SYSP macro.
* Changing to full function WebSphere MQ
* Reverting to previous versions
* Migrating from an earlier unsupported release of WebSphere MQ or MQSeries
===============================================
This section describes the things that you must consider if you are migrating a single queue manager from a previous version of WebSphere® MQ.
First class migration support is provided to WebSphere MQ for z/OS® Version 7.0 from WebSphere MQ for z/OS Version 6.0. This means you can restart a queue manager at WebSphere MQ Version 7.0 by replacing the executable code (for example, the STEPLIB data sets) with equivalent Version 7.0 libraries and then restarting the queue manager. When a backward migration PTF has been applied to Version 6.0 code, it is possible to fall back from Version 7.0 operation to Version 6.0.
Start of changeThe points below can be carried out before or after the initial stage (1) of migrating a single queue manager from a previous version of WebSphere MQ.
* Apply the Version 7.0 coexistence and backward migration PTFs to the Version 6.0 code.
* Restart production WebSphere MQ systems with this PTF-updated Version 6.0 code. Verify correct function before proceeding and review any special actions detailed in the PTFs. If you require fall back at this stage, use normal maintenance procedures to revert to the Version 6.0 code before PTF application.
End of change
Follow these steps to migrate a production queue manager from WebSphere MQ Version for z/OS Version 6.0 to WebSphere MQ Version for z/OS Version 7.0:
1. Install Version 7.0 early code. Refresh the early code level of all queue managers in the LPAR.
2. Restart production WebSphere MQ systems with Version 7.0 code. Verify correct function of existing applications before using any new Version 7.0 functions. If problems become apparent at this stage, fall back to the Version 6.0 code with backward migration PTFs that have been previously validated for your environment.
For a queue-sharing group, apply the Version 6.0 coexistence and backward migration PTFs to all members before you migrate any member to Version 7.0.
For releases earlier than Version 6.0, no backward migration support from Version 7.0 is provided. You can migrate a queue manager from a release earlier than Version 6.0 directly to Version 7.0, but if problems arise there is no good fall back capability. This is not good practice for production systems, but it might be sufficient for a test queue manager. See section Migrating from an earlier unsupported release of WebSphere MQ or MQSeries for further information. Ensure that production systems are fully migrated to Version 6.0 and stability is achieved before migration to Version 7.0.
* Migrating to WebSphere MQ for z/OS Version 7.0
You might need to perform some additional tasks when migrating from a previous version, depending 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 you need to perform.
* Migrating from Version 6.0
* Start of changeControlling new functionality and backward migration using the OPMODE propertyEnd of change
The availability of new functions and backward migration for WebSphere MQ for z/OS can be controlled using the OPMODE property in the CSQ6SYSP macro.
* Changing to full function WebSphere MQ
* Reverting to previous versions
* Migrating from an earlier unsupported release of WebSphere MQ or MQSeries
Comments
Post a Comment