Resolving migration problems when developing message flows

This topic contains advice for dealing with some common migration problems that can arise when developing message flows:

Your migrated message flow project contains .msgnode files

You do not know whether you need to migrate the Version 2.1 IBM primitives

An error message is issued when you save a message flow that contains MQe nodes

Start of change

MRM field is seen as NULL in Version 5.0 or later versions of the product

Related concepts
Message flows overview
End of change