A communication error is issued when you use the enqueue facility
Scenario: You use the enqueue or dequeue tools to put a
message on a queue, but an error message is issued indicating that there is
a communication error with the queue manager name.
Explanation: The WebSphere MQ queue
manager has not started.
Solution: Restart the WebSphere MQ queue
manager.
The enqueue facility is not picking up changes made to a message
Scenario: You are using the Message Brokers Toolkit's
message enqueue facility to put messages to WebSphere MQ queues.
You have updated a message and want to put the message to the queue, but your
changes do not seem to have been picked up.
Solution:
Close and then reopen your enqueue file.
Select the message that you want to put to the queue.
Save and close the enqueue file.
Select the menu next to the Put
a message to a queue icon.
Click Put message.
Click the enqueue file in the menu.
Click Finish.
This puts your updated message to the queue.
You do not know which header elements have any effect in enqueue
Scenario: When using the Enqueue editor, the accounting
token, correlation ID, group ID, and message ID in the message header do not
seem to have any effect.
Explanation: These fields have no effect because they are
not serialized properly.
Enqueue message files are still listed after they have been deleted
Scenario: Enqueue message files are still listed in the
drop-down menu after they have been deleted.
Explanation: Deleted enqueue files are not removed from
the drop-down menu. Selecting these files has no effect.
The MRM parser has failed to parse a message because two attributes
have the same name
Scenario: Two attributes in different name spaces have identical
names. Error message BIP5117 is issued.
Explanation: The MRM (Xerces) parser has failed to parse
the message.
Solution: Modify the attribute names so that they are not
identical. This is a know problem with the Xerces parser.
You encounter problems when messages contain EBCDIC New Line characters
Scenario: If your bit stream input message contains EBCDIC
New Line (NL) characters, problems might arise if your message flow changes
the target CCSID to an ASCII CCSID. For example, during conversion from CCSID
1047 (EBCDIC used for z/OS Open Edition)
to CCSID 437 (US PC ASCII), an NL character is translated from hex '15' to
hex '7F', which is an undefined character. This is because there is no corresponding
code point for the New Line character in the ASCII code page.
Solution: You can overcome the problem in the following case:
On a system where the queue manager uses an ASCII codeset, you can make
sure that incoming messages do not contain any EBCDIC NL characters by:
Specifying that WebSphere MQ performs the
conversion at the input node
Setting the queue manager attribute to convert NL to Line Feed (LF)
Problems when using code page translation on HP-UX
Scenario: You experience code page translation problems
on HP-UX.
Solution: Check the WebSphere
MQ queue
manager attribute CodedCharSetID. The default value
for this attribute is 1051. Change this to 819 for queue managers that host WebSphere Event Broker components.