Resolving problems when using messages

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

A communication error is issued when you use the enqueue facility

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

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

An XML message loses carriage return characters

The broker is unable to parse an XML message

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

Start of change

Error message BIP5004 is issued by the XML parser

End of change

Error message BIP5005 is issued by the Compute node

A message is propagated to the Failure terminal of a TimeoutControl node

Message processing fails within a TimeoutNotification node

An MRM CWF message is propagated to the Failure terminal

Start of change

Problems with XML attributes

XML tags are written where XML attributes are expected, and vice versa.

End of change

An MRM XML message exhibits unexpected behavior

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

You encounter problems when messages contain EBCDIC New Line characters

The MIME parser produces a runtime error while parsing a message

Runtime errors are issued when you write a MIME message from the logical message tree

Start of change

Output message has an empty message body

End of change

Error message BIP5651 is issued when receiving a SOAP with Attachments message from a WebSphere Application Server client

WebSphere Application Server produces an error when receiving a SOAP with Attachments message

Problems when using code page translation on HP-UX

Related reference
TimeoutControl node