Resolving problems when using messages

This topic contains advice for dealing with some common problems that can arise when using messages:

The MRM parser has failed to parse a message because two attributes have the same name

A communication error is issued when you use the enqueue facility

The enqueue facility is not picking up changes made to a message

Error messages are issued when you use the enqueue facility to put a message on a remote queue

You do not know which header elements have any effect in enqueue

Enqueue message files are still listed after they have been deleted

The ESQL transform of an XML message gives unexpected results

Error message BIP5005 is issued by the Compute node

An MRM CWF message is propagated to the failure terminal

An MRM XML message exhibits unexpected behavior

You encounter problems when messages contain EBCDIC New Line characters

Start of change

The broker is unable to parse an XML message

End of change

Unexpected characters are displayed when using the XMLTransformation node on z/OS