| Author |
Message
|
| mutley |
 Posted: Wed Jun 25, 2003 2:37 am Post subject: How to decipher MQ trace files? |
 |
|
Novice
Joined: 12 Jun 2003
Posts: 13
|
I have had a look in the manuals and support pacs but haven't been able to find any mention of how to decipher these files. I'm only interested in the MQI calls that are being made and any options specified along with them. In the trace files there seem to be at least three mentions of the each MQI verb called. What is confusing is that especially on the MQCONN call, MQCONNX is mentioned 2 out of the three times!
Does anyone have information on how to do this?
Regards
Neil |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Thu Jun 26, 2003 6:52 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Trace files and tracing in general is meant only to be used by the IBM support team to assess any possible problems that you might have encountered. These are not meant for the end user and hence i am not sure what exactly you are looking for here.
As for end user, you have enough tools/mqi api that can help you assess whats going on.
Hope this helps.
Cheers
Kumar |
|
| Back to top |
|
|
| mutley |
| Posted: Fri Jun 27, 2003 2:13 am Post subject: |
|
|
Novice
Joined: 12 Jun 2003
Posts: 13
|
I'm trying to only understand a subset of the traces - the api call and options - I'm not interested in the O/S interaction stuff. I would have thought IBM would be comfortable explaining this.
The API exits stuff only run against the server, so I understand, but I'm still trying to see the MQCONNX call with options at this point. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Fri Jun 27, 2003 5:23 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
As i explained in my previous response, you have more than enough tools to analyze a problem being an end user. If your intention is just to know what options are being passed out into MQCONNX, just debug and take a look at it or you could as well printf everything just before and after the call to see whats going on.
As for the trace files, even though they are readable by the end user, they are meant only as a resource to assist the tech support guys from IBM to figure out whats going on. What you see in there is the tracing of all the function calls made within MQ which is hard to understand being an end user.
Hence my advise is to use the debugger. If you are really interested in understanding what the trace file's having, you need to make a call to the IBM helpdesk. I don't think anyone would be able to help you out here with it, unless someone from IBM with the same platform group as you are using are monitoring this thread.
Hope this helps.
Cheers
Kumar |
|
| Back to top |
|
|
| mutley |
| Posted: Fri Jun 27, 2003 5:31 am Post subject: |
|
|
Novice
Joined: 12 Jun 2003
Posts: 13
|
I'm afraid this is an existing application written by Microsoft (level8) called the MSMQ Bridge that I am specifically trying to understand so I can't debug it.
Thanks anyway
Neil |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Jun 27, 2003 9:06 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The details of the trace files usually aren't given out. What is the error that you are seeing that is causing you to look at the trace? If you could post some details on the error, somebody might be able to get you an answer. |
|
| Back to top |
|
|
| mutley |
| Posted: Wed Jul 02, 2003 5:55 am Post subject: |
|
|
Novice
Joined: 12 Jun 2003
Posts: 13
|
Ok, here is some output.
This is a full trace of amqsputc.exe which uses a MQCONN?
00001204 16:15:05.443264 1220.1 --{ MQCONN
00001205 16:15:05.443356 1220.1 ---{ trmzstMQCONNX
00001206 16:15:05.443386 1220.1 MQCONNX 'MSMQ'
............
0000120B 16:15:05.443783 1220.1 W2K Using CoGetObjectContext [pthconn=0 hconn=-999 hobj=-998 (-998) cc=-997 rc=-996]
0000120C 16:15:05.443863 1220.1 LoadLibrary Complete [pthconn=0 hconn=-999 hobj=-998 (-998) cc=-997 rc=-996]
0000120D 16:15:05.443963 1220.1 mtsCheck in mqconnx - no object context, using LEGACY [pthconn=0 hconn=-999 hobj=-998
.............
00001418 16:15:05.534131 1220.1 --} DoConnect (rc=OK)
00001419 16:15:05.534153 1220.1 --} trmzstMQCONNX (rc=OK)
0000141A 16:15:05.534175 1220.1 --} MQCONN (rc=OK)
This is the output of the MSMQBridge connecting - which definitely uses MQCONN:
00000170 14:55:34.399994 616.2 --} DoConnect (rc=OK)
00000171 14:55:34.400016 616.2 --} trmzstMQCONNX (rc=OK)
00000172 14:55:34.400038 616.2 --} MQCONN (rc=OK)
|
|
| Back to top |
|
|
|
|
