| Author |
Message
|
| bindu |
 Posted: Tue Dec 21, 2004 10:43 am Post subject: MQSI Debugging...Urgent |
 |
|
Voyager
Joined: 07 May 2004
Posts: 97
|
Hi,
When I am trying to debug my flow by using mqsichangetrace, mqsireadlog and mqsiformatlog. I got the follwoing message on the file...
'Timestamps are formatted in local time, 300 minutes before GMT.
Threads encountered in this trace: '
Any help.
Thanx,
Bindu |
|
| Back to top |
|
 |
| RocknRambo |
| Posted: Tue Dec 21, 2004 10:51 am Post subject: |
|
|
Partisan
Joined: 24 Sep 2003
Posts: 355
|
can u post the detailed the error message . are u using the function LocalTimeZone or so ??
any ExceptionList if created ??
-RR |
|
| Back to top |
|
|
| bindu |
| Posted: Tue Dec 21, 2004 10:59 am Post subject: MQSI Debugging...Urgent |
|
|
Voyager
Joined: 07 May 2004
Posts: 97
|
Hi,
i used mqsichangetrace at /var/mqm
for reading that we have to give one trace file name i.e. i gave out.trace
and i used outfmt.trace for formating ...i found the folowing message in that file.
Timestamps are formatted in local time, 300 minutes before GMT.
Threads encountered in this trace:
...actuvally that flow should contain the flow process details.
Thanx,
Bindu |
|
| Back to top |
|
|
| JT |
| Posted: Tue Dec 21, 2004 11:04 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
That's an informational message that generally appears at the top of the output trace file.
If that's one of the few entries in your trace file, then you either:
- didn't set the trace correctly on the msqichangetrace command
- didn't identify the correct Execution Group on the mqsireadlog command
- didn't specify the correct output file that was generated via the mqsireadlog, on the mqsiformatlog command
- the component being traced, wasn't executed
Take a look at the IA0R- Reformat User Trace Utility supportpac, which does this all for you in one neat script. |
|
| Back to top |
|
|
| RocknRambo |
| Posted: Tue Dec 21, 2004 3:01 pm Post subject: |
|
|
Partisan
Joined: 24 Sep 2003
Posts: 355
|
I use mqsiformatlog to .txt rather than... .trace
like
| Quote: |
| mqsiformatlog -i err.log -o err.txt |
wanna try this....what comes of it
-RR |
|
| Back to top |
|
|
| ayanc |
| Posted: Wed Dec 22, 2004 4:25 am Post subject: |
|
|
Voyager
Joined: 15 Nov 2004
Posts: 88
|
Hi,
It seems that no trace operation has been performed. My guess is that no input message has been sent to the queue before using mqsireadlog command.
I think you need to follow the following steps in sequence:
1. Put the message flow into debug mode
2. Put an input message to the queue
3. Use mqsireadlog command
4. Use mqsiformatlog command
5. View the final file.
For mqsireadlog you may use:
mqsireadlog <Broker> -u -e <Exec Grp> -o filename.xml
followed by
mqsiformatlog -i filename.xml -o tracefile.log
You need to view the tracefile.log in any text editor.
It is recommeded that you use the following command to flush of the log and prepare it for next round of trace operations.
mqsichangetrace <Broker> -u -e <Exec Grp> -r
Hope this helps.
Ayan |
|
| Back to top |
|
|
|
|
