Migrating or importing message flows and message sets:

This topic contains advice for dealing with some common problems that can arise when importing or migrating resources:

The mqsimigratemsgflows command gives unexpected results

Message flows that refer to a migrated user-defined node have connection errors

Message flows that have been migrated from Version 2.1 cannot resolve subflows

A broker has been migrated from Version 2.1 to Version 6.0 and some message flows are now stopped

After migration, message flows cannot locate a user-defined node

Deployment of message flows fails when you migrate them from Version 2.1 to Version 6.0

Warnings are displayed for message flows that you have imported from Version 2.1 to Version 6.0

The mqsimigratemsgsets command gives unexpected results

You get import problems with imported message sets