MQ Migration Process steps from lower version to H

2019-09-14 20:52发布

问题:

Current version running is MQ7 in windows 2008 server. What to know about migration process steps from MQ7 to MQ8/MQ9?.New Version of MQ8/MQ9 Server to be installed and how existing Queue definition can be migrated?

  1. Will Server Installation take care of QM definition also?
  2. windows 2008 server will be good for mq9?
  3. There is a MQ-Client7 contacting MQ-Server7, so if we upgrade MQ7 to MQ9 then MQ-Client also will be upgraded to MQ9?
  4. There will be any issue in contacting MQ9-Client to MQ7 Server?
  5. dspmqver will give MQ server details , how to verify MQ-Client version?

回答1:

If you install the new version (V8 or V9) as an upgrade to the V7 installation on the same machine then then next time you start the queue manager it will be migrated to the new version.

If you install the new version alongside the V7 installation on the same machine, then you have to use the setmqm command to force the queue manager to move from V7 to the new version.

If you install the new version on a completely different machine, the no automatic migration can take place. You will have to create a brand new queue manager and then copy across the definitions from the old one.

The command to export all the object definitions is:

dmpmqcfg -m QM1 -x all > DEFS.mqs

The command to import all the object definitions is:

runmqsc QM1 < DEFS.mqs

The system requirements (e.g. minimum O/S levels) are documented by IBM here.

There is no requirement for the MQ Client to be the same version as the MQ Queue Manager. The MQ Client can be a higher version or a lower version than the MQ Queue Manager and still operate perfectly. The only thing to remember if the MQ Client is a higher version than the MQ Queue Manager is that new features cannot yet be used.

You can see the version of the MQ Client being used when it connects to the queue manager by looking in DISPLAY CHSTATUS for the field called RVERSION.



标签: ibm-mq