Collect WebSphere MQ MustGather data to solve data conversion problems on HP NonStop Server

Resolving The Problem

Please answer these questions about the problem and then follow the steps below:

• What data conversion problem did you observe on the system?
• What is the MQMD.Format of the message and its original MQMD.CodedCharSetId (CCSID)?
• What is the intended MQMD.CodedCharSetId to which the message should be converted?
• Which specific characters in the message are invalid, and which did you expect to see instead?

Step 1: Generate Data

If the data conversion problem is reproducible or is happening right now, generate data to provide more information about the problem:

1. Guardian users should run the osh TACL command to switch to the OSS environment. Then, browse the message immediately after it has been put to WebSphere MQ using a program like the opt/mqm/samp/bin/amqsbcg sample. It is important to see the message in hex in order to examine the MQMD header and the byte values of the message data. For example:



Browsing My.Queue on queue manager QMA


osh> amqsbcg My.Queue QMA > My.Queue.browse.txt




2. Alternatively, generate a trace of the queue manager while the application is putting the message.



3. If the message contents are corrupted while flowing over an MQ channel with CONVERT(YES), generate a trace of the queue manager while the message is flowing across the sending channel.



4. Browse the message using a program like the opt/mqm/samp/bin/amqsbcg sample program just before it is retrieved by the target application.



5. If the message contents are corrupted when the target application gets the message, generate a trace of the queue manager while the application is getting the message.

Step 2: Collect Data

1. Record the MQ version and maintenance level.



2. Record the operating system version and maintenance level.



3. On the sending side, use runmqsc to record your queues, channels and channel status information. If any command gives an error, carry on with the others:

DISPLAY QMGR ALL
DISPLAY QLOCAL(*) ALL
DISPLAY QALIAS(*) ALL
DISPLAY QREMOTE(*) ALL
DISPLAY CHANNEL(*) ALL
DISPLAY CHSTATUS(*) ALL




4. On the receiving side, use runmqsc to record your queues, channels and channel status information. If any command gives an error, carry on with the others:

DISPLAY QMGR ALL
DISPLAY QLOCAL(*) ALL
DISPLAY CHANNEL(*) ALL
DISPLAY CHSTATUS(*) ALL




5. Use the sdcp script to package your files for IBM, including files containing the output from the commands listed in Step 1 and 2.

Step 3: Send Data to IBM

1. Send your data to the IBM ECuRep repository by email to websphere_support@ecurep.ibm.com, or by standard or secure HTTP or FTP.



2. While the data is transferring, send an email or use the IBM Service Request tool to update your PMR with your description of the problem and of the data you are sending.




A good description of the problem and the data is the most important information you can provide to IBM. Please do not send data without providing a description!



3. Contact your country representative if you need to speak to an IBM technical support representative, or in the US call 1-800-IBM-SERV. Refer to the IBM Software Support Handbook for more information on working with IBM.

Back to top