| Author |
Message
|
| ethirajesh |
 Posted: Wed Feb 02, 2011 11:50 pm Post subject: how to use mqsireadlog in message broker? |
 |
|
Apprentice
Joined: 04 Oct 2010
Posts: 46
|
Hi Friends,
I am trying read the log that is generated in Linux by message broker. When there is a exception in message flow, I am generating a error message describing the failure by reading the exception tree. Then I write to system logs by setting Trace node property "Local error log".
Now when I try reading this, it throws the error :
$ mqsireadlog WMQDQM06 -u -e WMQDQM06_SIH -o trace.xml
-ksh: mqsireadlog: not found [No such file or directory]
Why I am not able to run this command? Once I run this command how can I read 'specific error message' for a particular message?
Regards
Rajesh Ethiraj |
|
| Back to top |
|
 |
| vijayakumar |
| Posted: Thu Feb 03, 2011 1:04 am Post subject: |
|
|
Centurion
Joined: 01 Aug 2010
Posts: 101
|
Please check whether the mqsireadlog command is available in your unix path .
/opt/IBM/mqsi/version of the broker/bin .
$ mqsireadlog WMQDQM06 -u -e WMQDQM06_SIH -o trace.xml
-ksh: mqsireadlog: not found [No such file or directory]
In the above command -u is nothing but ur user trace .
I dont know the reason why u want to use mqsiread to read the logs written in syslog(Local error log) .
The mqsireadlog command is mainly used for User trace or service trace . Mainly used to get the trace information . |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Feb 03, 2011 4:11 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
doing the following wiil tell you is the command is valid
If that returns no results then you have not setup the broker command environment
To do that you need to 'source' the mqsiprofile script.
This is located in the bin directory when yuo installed the broker runtime
This is Unix/Linux 101 + Broker Runtime on Unix/Linux 101
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| ethirajesh |
| Posted: Thu Feb 03, 2011 8:40 pm Post subject: |
|
|
Apprentice
Joined: 04 Oct 2010
Posts: 46
|
| vijayakumar wrote: |
I dont know the reason why u want to use mqsiread to read the logs written in syslog(Local error log) .
The mqsireadlog command is mainly used for User trace or service trace . Mainly used to get the trace information . |
Whenever there is a exception I am having subflow to handle this. This will read the exception tree and builds a message describing the cause. This message is written to system logs, in Linux I am not able to read or see where is this error message is written. But in Windows I am seeing it.
My understanding is in Linux also it writes the error message, but not having a way to read that error message.
I checked under /opt/ibm/mqsi/7.0/, but there is no bin directory available under this.
But I found mqsireadlog is existing under "/opt/mqsi/7.0/bin" :
$ pwd
/opt/mqsi/7.0/bin
$ ls -ltr mqsireadlog
-rwxr-xr-x 1 bin mqbrkrs 216054 Jul 7 2010 mqsireadlog
$
Will this help Vijay? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 04, 2011 8:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
In your case talking to the sysadmin and having him help you look at the syslog might help. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Feb 05, 2011 6:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You have to source mqsiprofile.
 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Feb 05, 2011 9:17 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
You have to source mqsiprofile.
|
Something like I suggested on Thursday ?
| smdavies99 wrote: |
To do that you need to 'source' the mqsiprofile script.
|
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Feb 05, 2011 6:49 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| mqjeff wrote: |
You have to source mqsiprofile.
|
Something like I suggested on Thursday ? |
Felt it bore repeating.
|
|
| Back to top |
|
|
| hallmark |
| Posted: Tue Feb 08, 2011 3:44 am Post subject: |
|
|
Voyager
Joined: 10 Mar 2005
Posts: 76
|
| Quote: |
Whenever there is a exception I am having subflow to handle this. This will read the exception tree and builds a message describing the cause. This message is written to system logs, in Linux I am not able to read or see where is this error message is written. But in Windows I am seeing it.
|
I am assuming you are referring to messages in the windows event viewer...
You may find on 'nix' systems that some configuration is necessary with your syslog daemon to get your user/debug output from applications such as broker to be output to a logfile.
As someone here mentioned, speak to your unix admin on how this is done...syslog.conf might be a good starter for 10, but my unix exposure is limited to aix/linux so it could differ.
[/quote]
_________________
Rob |
|
| Back to top |
|
|
|
|
