Scenario: You use the Enqueue/Dequeue tools to put a message
on a queue, but you get the error message Cannot communicate with 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.
Select Put message.
Click the enqueue file in the menu.
Click Finish.
This puts your updated message to the queue.
You get error messages when using Enqueue to put a message on a remote
queue
Scenario: You get error messages when using Enqueue to put
a message on a remote queue. Messages include BIP0887The
[parameter] is not properly set in enqueue file [filename.enqueue] and BIP8096ECan
not enqueue message into queue [queue name] using queue manager [queue manager
name]. Reason: Check the enqueue file [filename.enqueue] for errors and try
again.
Explanation: Enqueue does not support putting a message
on a remote queue; the queue must be on the same machine as the Message
Brokers Toolkit.
You do not know which header elements have any effect in Enqueue
Scenario: When using the Enqueue editor, the accountingToken,
correlationId, groupId, and messageId in the message header do not seem to
have any effect.
Explanation: These fields are not properly serialized so
they have no effect.
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.
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 :
On a platform 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)