| Author |
Message
|
| kirani |
 Posted: Thu Jun 27, 2002 2:12 pm Post subject: mqsiformatlog failing on Cc machine. |
 |
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I am getting an error while running mqsiformatlog command on Control Center machine. The dialog box says ..
The procedure entry point SymFromAddr could not be located in the dynamic link library DBGHELP.dll.
I have dbghelp.dll file on my machine and I have compared the file size for mqsiformatlog.exe and dbghelp.exe file against WMQI server and they match. I have my PATH set to <wmqi_home>\Tool and <wmqi_home>\bin directory.
Any idea??
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
 |
| TorpedoSTu |
| Posted: Fri Jun 28, 2002 2:15 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
Kiran,
How big is the output from mqsireadlog because .....
I've seen this where the output from mqsireadlog is too big for mqsiformatlog to handle.
I can only suggest that you move the flow your debugging to it's own exe group and trace it there. run a mqsichangetrace before retrying hte flow.
The other reason for this could be that there is a runaway loop within the message flow producing too much output.
Regs
Stuart |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Fri Jun 28, 2002 5:39 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
I believe DBGHELP.DLL is used in producing the stack trace for an abend in WMQI, so, an abend is occurring but some code needed by the abend handler is not being resolved. This gives us two problems:
1. What's causing the abend. Try this out with a smaller log file (just cut down the entries in the one you have but in a way which preserves the XMLs structural integrity, no I'm not a trekkie).
2. What's up with DBGHELP.DLL.
Is there a dbghelp.dll file in your wmqi bin directory on this (cc) machine. If not, try copying the one from the wmqi bin directory on the server and see do you get an abend file produced when the actual failure occurs. |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Jun 28, 2002 2:26 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Sturat,
The output of mqsireadlog is very small (15K). I don't know why is this command failing. I never ran this command before on my local workstation (Control Center machine).
Codecraft,
I re-copied the file DBGHELP.dll from WMQI server and guess what .. each time I ran this command, it asked for some new file, which is missing on my Control Center machine!! I ended up copying around 12-15 files from WMQI server and still it doesn't work!
I think IBM should really test each and every command before the software is released. We end up copying many files from WMQI server, which should have been a part of standard WMQI Control Center Installation.
Hope they will fix this in future releases.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| CodeCraft |
| Posted: Fri Jun 28, 2002 2:58 pm Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
Kirani,
If you have formal support entitlement, pls. report this. If not, could you produce a reportable problem description and send it to me, including a list of error messages and files you had to copy, and, the trace file you had the problem with (zip it all up). Unfortunately, a lot of this stuff crosses my path but falls outside my direct control or area of responsibility and if I personally deal with each and every case it would be far far too much to handle!
Thanks,
Carl. |
|
| Back to top |
|
|
| bindu |
| Posted: Tue Dec 21, 2004 10:41 am Post subject: MQSI Debugging...Urgent |
|
|
Voyager
Joined: 07 May 2004
Posts: 97
|
Hi,
When I am trying to debug my flow by using mqsichangetrace, mqsireadlog and mqsiformatlog. I got the follwoing message on the file...
'Timestamps are formatted in local time, 300 minutes before GMT.
Threads encountered in this trace: '
Any help.
Thanx,
Bindu |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Dec 21, 2004 4:09 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Nothing was traced. Make sure you turn on the trace for the correct Broker and Execution Group. The names ARe CasE SenSITiVe.
And DON'T post the same question twice.  Especially by hijacking a different thread.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
