Formatting trace

The trace information 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.

WebSphere Business Integration Event Broker provides the command mqsiformatlog to format the trace information to a flat file, so that you can view it using a text editor.

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 timestamp and a WebSphere Business Integration Event Broker message that contains a number (for example, BIP2622) and a text string containing variable inserts.

Details of the mqsiformatlog command (which, on z/OS, is run by customizing the BIPJLOG job) are described in mqsiformatlog command.

Example: formatting user trace information on Windows

On Windows, to format the trace file created in Starting user trace, enter the command mqsiformatlog -i trace.xml -o formattrace.log where:
-i
specifies the input file (in this case, trace.xml)
-o
specifies the output file (in this case, formattrace.log)
This command reads the trace information in the file trace.xml, formats it, and writes it to the file formattrace.log. The following example shows a portion of the output of the mqsiformatlog command for a normal level trace file.
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
Related concepts
Trace