| Author |
Message
|
| bond_02 |
 Posted: Mon Dec 25, 2006 3:54 am Post subject: List the 6 methods/ ways to determine problems/ debug in MQS |
 |
|
Apprentice
Joined: 21 Dec 2006
Posts: 39
Location: kolkata
|
| List the 6 methods/ ways to determine problems/ debug in MQSI. |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Mon Dec 25, 2006 4:24 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| bond_02 |
| Posted: Mon Dec 25, 2006 4:51 am Post subject: i am interested to know more |
|
|
Apprentice
Joined: 21 Dec 2006
Posts: 39
Location: kolkata
|
| Michael Dag wrote: |
| why? what's the prize? |
sir,
i am freshers software developer from india.I know the 3/4 steps because i use MQI V 2.But the fact is that i am interested to know more if any.sorry to give u prize! |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Dec 25, 2006 5:00 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
so you don't know if there are actually 6 methods?
list the ones you know, and someone might point you to other methods 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| bond_02 |
| Posted: Mon Dec 25, 2006 5:06 am Post subject: using Trace node, Event logs,User and service traces |
|
|
Apprentice
Joined: 21 Dec 2006
Posts: 39
Location: kolkata
|
| Michael Dag wrote: |
so you don't know if there are actually 6 methods?
list the ones you know, and someone might point you to other methods |
using Trace node, Event logs,User and service traces
User and service traces
the associated mqsi commands:
mqsichangetrace BROKER -u -l debug -e default
mqsireadlog BROKER -u -e default -o try
mqsiformatlog -i try -o try1
notepad try1
exit
making a batch file and running it. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Dec 25, 2006 5:08 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
you should move to V6 also! V2 is way obsolete and no longer supported!
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Bill.Matthews |
| Posted: Mon Dec 25, 2006 9:05 am Post subject: |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
| Michael Dag wrote: |
| you should move to V6 also! V2 is way obsolete and no longer supported! |
and then you can add the interactive debuggers to your list.
_________________
Bill Matthews |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Dec 25, 2006 9:33 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
But what you will find with v6, is that you will still do User Traces to map the complete path of the flow.
The Visual debugger is neat, but I will trace when it is tricky. That is the only way to know for sure.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Dec 25, 2006 9:53 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Here is a good book to start with:
http://www.redbooks.ibm.com/abstracts/SG247137.html?Open
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 25, 2006 12:26 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I've never found it important to know how many different ways there are of troubleshooting.
I always stop looking for new ways once I've found the problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
