This topic explains how to restore components and resources that you have migrated from Version 2.1 products back to their original state.
When you revert a broker from Version 6.0 to Version 2.1, message sets are deleted, so you must redeploy them. You are reminded to do this by warning message BIP8688, which appears when you run the mqsimigratecomponents command.
When you revert a broker from Version 6.0 to Version 2.1 on z/OS, retained publications are deleted.
After migration to Version 6.0, if you have deployed any message flows that use new Version 6.0 functions, such as new nodes or new ESQL syntax, those message flows will not start if your broker is reverted to Version 2.1. Other message flows in your broker that do not use new Version 6.0 functions will continue to run.
Due to coexistence requirements, you can restore the Configuration Manager to Version 2.1 only if you have not migrated any brokers to Version 6.0. If you restore the Configuration Manager to Version 2.1, you must also restore the Message Brokers Toolkit to Version 2.1.
The following sections describe how to restore the Message Brokers Toolkit and runtime components to Version 2.1.
Use the -s and -t parameters of the mqsimigratecomponents command to migrate components from Version 6.0 to Version 2.1. Specify Version 6.0 for the source version parameter (-s) and Version 2.1.0.8 for the target version parameter (-t). See the mqsimigratecomponents command topic for detailed information about these parameters and the format to use when specifying version numbers.
mqsimigratecomponents Broker -t 2.1.0.8Warning message BIP8688 might be displayed, warning you to redeploy your message sets.
mqsimigratecomponents UserNameServer -t 2.1.0.8
If you restore the Configuration Manager to Version 2.1, you must also restore the Message Brokers Toolkit and any brokers to Version 2.1.
The Version 6.0 Configuration Manager does not use the DB2 database that was used by the Version 2.1 Configuration Manager; if you restore to Version 2.1, the original database is used again. This means that any configuration changes that you made after you migrated the Configuration Manager to Version 6.0 will be lost. This can leave your domain in an inconsistent state, forcing you to rebuild and redeploy all of your brokers in order to regain a consistent state. After you have migrated your Configuration Manager to Version 6.0, check carefully that the Message Brokers Toolkit and Configuration Manager are working correctly before you attempt any further configuration changes or before you migrate any brokers.
If you have moved the Configuration Manager's queue manager during migration, you must keep the new queue manager when you restore, unless you restore your entire domain from a backup. If you have moved the Configuration Manager onto an operating system other than Windows, you cannot restore it to Version 2.1 unless you restore your domain from a backup.
mqsimigratecomponents ConfigMgr -t 2.1.0.8Your Version 6.0 Message Brokers Toolkit will no longer work; you must use a Version 2.1 Message Brokers Toolkit instead.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah23892_ |