| Author |
Message
|
| WBI_user |
 Posted: Tue Apr 08, 2008 5:28 am Post subject: Input to mqsireadlog |
 |
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
We are running WMB V6 CSD5 on AIX
In /var/mqsi/common/log directory we noticed most of the trace.bin.0 files are empty except a couple of entries like this
PR123B1.2a7aeb65-1801-0000-0080-97ef3bdc18e8.userTrace.bin.0
with 64261 bytes
PR123B1.3eddea65-1801-0000-0080-97ef3bdc18e8.userTrace.bin.0
with 23453 bytes
We are not sure if these was a result of some problems. What we know from running user traces is we have to use mqsireadlog to get the file into xml format and then use mqsiformatlog to format the xml output.
I need some help on how to specify the input parameter to mqsireadlog to format the usertrace.bin.0 file.
I know that component name should probably be PR123B1 which is our broker. But what is the execution group name. I assume this is a user trace. If this is a service trace, thne what should be the subcomponent name? |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Tue Apr 08, 2008 8:18 pm Post subject: Re: Input to mqsireadlog |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
|
| Back to top |
|
|
| abhishekpreddy |
| Posted: Tue Apr 08, 2008 11:19 pm Post subject: |
|
|
Apprentice
Joined: 02 May 2007
Posts: 49
|
Hi ,
As per my knowledge , the Broker never writes any Trace logs files on its own , when you have the flows running in debug mode , you have to implicitly collect the logs using the mqsireadlog command , I am not sure how you get the logs files which you mentioned directly |
|
| Back to top |
|
|
| mqpaul |
| Posted: Wed Apr 09, 2008 2:36 am Post subject: mqsireadlog works out which files it needs |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
The broker will write several files depending on user and service trace settings. You aren't expected to process those files directly (the mapping between the log file names and contents and broker components isn't trivial). The mqsireadlog program will work out which files it needs to read according to the parameters you pass and the broker configuration.
AFAIR, the broker doesn't spontaneously write user log or trace files, even if there are errors. It only writes them if you enable user or service trace levels greater than "NONE" with mqsichangelog or the toolkit. So if your files contain data, it's because someone asked the broker to collect it.
The "-e" execution group parameter is optional on mqsireadlog - if you omit it, it formats the log for all groups traced in the chosen broker. So something like:
| Code: |
mqsireadlog PR123B1 -f -o userTrace.xml
mqsireadlog -i userTrace.xml -o userTrace.txt |
should format those trace files.
See the broker HelpCenter item "mqsireadlog command" for more details on its parameters.
_________________
Paul |
|
| Back to top |
|
|
| AJStar |
| Posted: Wed Apr 09, 2008 4:17 am Post subject: Re: mqsireadlog works out which files it needs |
|
|
Acolyte
Joined: 27 Jun 2007
Posts: 64
|
| mqpaul wrote: |
| It only writes them if you enable user or service trace levels greater than "NONE" with mqsichangelog or the toolkit. |
I guess you meant mqsichangetrace !!! 
_________________
Regards
AJ |
|
| Back to top |
|
|
| WBI_user |
| Posted: Wed Apr 09, 2008 4:46 am Post subject: |
|
|
Partisan
Joined: 07 Aug 2001
Posts: 386
|
| Thanks for all the responses. Since the broker will not write the file unless someone ask it it to do so, I think I can safely ignore the files. However I'll still to see if I can format them just for my own interest. |
|
| Back to top |
|
|
|
|
