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

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

A message flow that contains an EVAL statement no longer deploys

Comparing an empty XML tag with NULL fails

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

A CAST of blank data to DECIMAL does not give the same results as Version 2.1

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

ESQL DECIMAL values no longer have leading or trailing zeros

Rounding of ESQL DECIMAL values has changed

Labeled statements in ESQL generate errors

The task list shows unresolved reference warnings for ESQL code

Deploying a message flow fails with BIP2935E

Deploying a message flow fails with BIP2912E

Deploying a message flow fails with BIP2493E

An MRM parent field has NULL value

MRM XML messages include a namespace on the root tag

MRM XML messages include invalid x'00' NUL bytes

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

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

Data patterns in TDS messages are rejected

Duplicate global elements are not allowed

Data Element Separation set to Tagged Fixed Length generates errors

MQRFH2 NameValueData empty tags are written in the short form

Execution groups retain many open queue handles

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:23:31

au16661_