| Author |
Message
|
| solomon_13000 |
 Posted: Thu Oct 02, 2008 8:01 am Post subject: Trace route messaging facility. |
 |
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| According to an article we use the trace route messaging facility if the messages are cought in an infinite loop due to an application programming error. What are the other possible scenario whereby the trace route messaging facility can be used? |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Thu Oct 02, 2008 9:14 am Post subject: Re: Trace route messaging facility. |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Fri Oct 03, 2008 1:33 am Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| so if the queue manager error log and fdc file does not explain the problem or more the less they are the same in terms of explanation, then we will issue the strmqtrc command?. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Oct 03, 2008 2:27 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
strmqtrc is the command to turn on tracing not to do trace routing.
In general, you would never turn on tracing unless you were encountering some kind of problem and were working with IBM Support to resolve it. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Fri Oct 03, 2008 5:09 am Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| I found the command which is dspmqrte. It is used to generate a trace route message into the queue manager network. Using the trace route message activity information can be collected. Also the route in which the trace route message took can be determent. |
|
| Back to top |
|
|
|
|
