Collecting information for data conversion problems on Multiplatforms

If you need assistance to resolve a problem with data conversion on Multiplatforms, you might need to collect additional troubleshooting information to include with your support case to help find a solution to the problem.

Before you begin

Before you start this task, answer the following questions about the problem:

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?

About this task

If the data conversion problem is happening right now, or if you are able to reproduce it, you can generate data to provide more information about the problem.

After collecting the troubleshooting information, you can send it to IBM®.

Procedure

Browse the message immediately after it has been put to an IBM MQ queue using a sample program such as amqsbcg.
It is important to see the message in hexadecimal in order to examine the MQMD header and the byte values of the message data. For example, to browse messages on a queue called 'Target.Queue' on queue manager called 'QMA', enter this command:
```
amqsbcg Source.Queue QMA > Source.Queue.browse.txt
```
Generate a trace of the queue manager while the application is putting the message:
If the message contents are corrupted while flowing over an IBM MQ channel with CONVERT(YES), generate trace of the queue manager while the message is flowing across the sending channel:
Browse the message using a sample program such as amqsbcg just before it is retrieved by the target application.
For example, to browse messages on a queue called 'Target.Queue' on queue manager called 'QMA', enter this command:
```
amqsbcg Target.Queue QMA > Target.Queue.browse.txt
```
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:
Collect the IBM MQ data.
You can do this either automatically or manually:
- Collect the data automatically by using the runmqras command as described in Collecting troubleshooting information automatically with runmqras to collect the data for both sides of the channel. Be sure to collect the runmqras defs and trace sections, and to specify your case number as shown in the following example:
```
runmqras -section defs,cluster,trace -qmlist QMA -caseno TS001234567
```
- Alternatively, collect the data manually as described in Collecting troubleshooting information manually.
Send the information that you have collected to IBM.

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

For FTP and email instructions, see Exchanging information with IBM Software Support.

To open or update a case, go to the IBM My Support site.
Note: Always update your case to indicate that data was sent.

If you need to speak with IBM Software Support, contact your country representative. If you need to speak with IBM Support in the US, you can call 1-800-IBM-SERV.