| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How can i see the trace on AIX broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| venugp |
 Posted: Thu Sep 19, 2002 1:00 pm Post subject: How can i see the trace on AIX broker |
 |
|
Apprentice
Joined: 03 Sep 2002
Posts: 31
|
I am trying to activate the trace on my message flow with the broker running on AIX server and cotrol centre on local workstation.
I have tried with different options but i couldn't see the exact trace,
Can any body help with exact steps i have to do to make it work trace for my message flow(broker on AIX) and where i can see these traces.
Thnaks
venu. |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Sep 19, 2002 2:10 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Enabling Trace on Message Flows
To enable trace on a message flow,
1. Using Control Center goto Operations tab.
2. If you don't see your message flow in right pane, click on refresh button on the toolbar.
3. Now right-click on your message flow, from the pop-up menu select User Trace->Debug This will send a request message to enable trace on this message flow to the broker.
4. Swith to your log view and make sure your request is processed successfully by clicking on refresh button on the toolbar.
5. Come back to your Operations view and select refresh again, now you should see a this small icon in front of the message flow. This means debug is enabled on your message flow.
6. Now run your message flow by sending messages on the input queue.
7. Next time when you do a deploy of your message flow, trace will be disabled on that message flow/execution group.
Extracting Trace
To extract trace for the message flow, follow these simple steps on broker machine:
1. goto command prompt and make sure mqsireadlog and mqsiformatlog executables are in your path.
2. run command mqsireadlog to extract log. For example,
| Code: |
| mqsireadlog <broker_name> -u -e <eg_name> -o egname.out |
3. run command mqsiformatlog to format the extracted trace. For example,
| Code: |
| mqsiformatlog -i <egname>.out -o <egname>.txt |
file <egname>.txt will contain trace output for your message flow.
_________________
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 |
|
|
| venugp |
| Posted: Thu Sep 19, 2002 4:07 pm Post subject: |
|
|
Apprentice
Joined: 03 Sep 2002
Posts: 31
|
Kiran.
I am have enabled the trace in noraml and debug mode too and i am getting informative text from that like the below one
2002-09-19 20:03:56.953998 1548 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'MSG-FLOW1.MQInput1' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'MSG-FLOW1.MQInput1' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2002-09-19 20:03:56.953998 1548 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'MSG-FLOW1.MQInput1' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'MSG-FLOW1.MQInput1' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
I am not seeing exactly where my code is going wrong so is there any thing i am missing.
Thank You,
venu. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Sep 19, 2002 4:55 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
venu,
What exact problem you are having with your message flow?
You will have to go thru each line of your trace file and see what is going wrong. You could try searching for fail or error in this trace file.
_________________
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 |
|
|
| venugp |
| Posted: Thu Sep 19, 2002 7:12 pm Post subject: |
|
|
Apprentice
Joined: 03 Sep 2002
Posts: 31
|
Kiran,
I am getting the trace and i am in the process of trying to find out the problem, Any how thanks for your help.
VENU. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
