Use the mqsiformatlog command to format trace information.
The trace information that is generated by the mqsireadlog command is not easy to read unless you use an XML viewer (such as an Internet browser) or an XML editor that understands the document type descriptor (DTD) in the file.
The mqsiformatlog command takes a file generated by the mqsireadlog command as input, and flattens the XML log into structured records. It also retrieves the inserts for the XML message in your current locale. You can direct the formatted output to a file, or view it in the command line window.
Each trace entry contains a time stamp and an IBM Integration Bus message that contains a number (for example, BIP2622) and a text string containing variable inserts.
To format the service trace file for an integration server, enter the command
mqsiformatlog -i </path/to/output.xml> -o </path/to/output.txt>
where:
On Windows, to format the trace file that is created in Starting user trace, enter the command
mqsiformatlog -i trace.xml -o formattrace.log
where:
Timestamps are formatted in local time, 330 minutes past GMT.
2003-06-19 11:30:29.795999 2852 UserTrace BIP2632I: Message received and
propagated to 'out' terminal of MQ Input node 'Video_Test.VIDEO_XML_IN'.
2003-06-19 11:30:29.795999 2852 UserTrace BIP6060I: Parser type 'Properties'
created on behalf of node 'Video_Test.VIDEO_XML_IN' to handle portion of incoming
message of length
0 bytes beginning at offset '0'.
2003-06-19 11:30:29.795999 2852 UserTrace BIP6061I: Parser type 'MQMD'
created on behalf of node 'Video_Test.VIDEO_XML_IN' to handle portion of incoming
message of length '364' bytes beginning at offset '0'. Parser type selected based
on value 'MQHMD' from previous parser.
2003-06-19 11:30:29.795999 2852 UserTrace BIP6061I: Parser type 'MRM'
created on behalf of node 'Video_Test.VIDEO_XML_IN' to handle portion of incoming
message of length '650' bytes beginning at offset '364'. Parser type selected based
on value 'MRM' from previous parser.
2003-06-19 11:30:29.795999 2852 UserTrace BIP2537I: Node 'Video_Test.Extract
Fields':
Executing statement 'BEGIN ... END;' at (.Video_Test_Compute.Main, 2.2).
2003-06-19 11:30:29.795999 2852 UserTrace BIP2537I: Node 'Video_Test.Extract
Fields':
Executing statement 'SET OutputRoot = InputRoot;' at (.Video_Test_Compute.Main, 7.3).
2003-06-19 11:30:29.795999 2852 UserTrace BIP2538I: Node 'Video_Test.Extract
Fields':
Evaluating expression 'InputRoot' at (.Video_Test_Compute.Main, 7.20).
2003-06-19 11:30:29.795999 2852 UserTrace BIP2568I: Node 'Video_Test.Extract
Fields':
Performing tree copy of 'InputRoot' to 'OutputRoot'.
...
2003-06-19 11:30:29.827999 2852 UserTrace BIP4124I: Message propagated to
'out' terminal of Compute node 'Video_Test.Extract Fields'.
2003-06-19 11:30:29.827999 2852 UserTrace BIP2638I: The MQ Output node
'Video_Test.VIDEO_OUT' attempted to write a message to queue 'VIDEO_OUT' connected
to queue manager ''. The MQCC was '0' and the MQRC was '0'.
2003-06-19 11:30:29.827999 2852 UserTrace BIP2622I: Message successfully
output by output node 'Video_Test.VIDEO_OUT' to queue 'VIDEO_OUT' on queue manager ''.
Threads encountered in this trace:
2852