Resolving problems when migrating or importing message flows and message sets

This topic contains advice for dealing with some common problems that can occur when you import or migrate message flows and message sets:

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 after migration from Version 2.1

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

The mqsimigratemsgsets command gives unexpected results

You get import problems with imported message sets

Start of change

Comparison of MRM message trees does not give the same results as Version 2.1

End of change
Start of change

A message flow that contains an EVAL statement no longer deploys

End of change
Start of change

Comparing an empty XML tag with NULL fails

End of change
Start of change

An exception is thrown when you CAST a CHAR to TIME or TIMESTAMP

End of change
Start of change

An exception is thrown when you compare a TIMESTAMP with CHAR '-1'

End of change
Start of change

ESQL DECIMAL values no longer have leading or trailing zeros

End of change
Start of change

Rounding of ESQL DECIMAL values has changed

End of change
Start of change

Labeled statements in ESQL generate errors

End of change
Start of change

The task list shows unresolved reference warnings for ESQL code

End of change
Start of change

Deploying a message flow fails with BIP2935E

End of change
Start of change

Deploying a message flow fails with BIP2912E

End of change
Start of change

Deploying a message flow fails with BIP2493E

End of change
Start of change

An MRM parent field has NULL value

End of change
Start of change

MRM XML messages include a namespace on the root tag

End of change
Start of change

MRM XML messages include invalid x'00' NUL bytes

End of change
Start of change

MRM CWF fields are not padded with zeros and have unexpected justification

End of change
Start of change

A TDS message of length zero is written from a fixed length structure

End of change
Start of change

Data patterns in TDS messages are rejected

End of change
Start of change

Duplicate global elements are not allowed

End of change
Start of change

Data Element Separation set to Tagged Fixed Length generates errors

End of change
Start of change

MQRFH2 NameValueData empty tags are written in the short form

End of change
Start of change

Execution groups retain many open queue handles

End of change