Use the mqsiformatlog command to process the XML log created by mqsireadlog. The command retrieves and formats any messages that the XML log contains into a form suitable for the locale of the user invoking the command.
This command interprets an input log file that has been created on any system in a platform-independent code page, utf-8. Use it to produce formatted output from input log files transferred from other systems to the system on which you issue the command. If you use this facility, ensure that you use a file transfer program that does not convert the data (for example, by specifying a binary transfer option).
You can direct the output to a file, or to the command shell.
Output written by this command (to file or stdout) is written in a code page suitable for the current user locale.
The user ID used to invoke this command must have read access to the input file, and write access to the output file.
On Linux and UNIX systems, the user ID must be a member of the mqbrkrs group.
mqsiformatlog -i trace.xml -o formattrace.log
The following extract illustrates the output generated by this command:
Timestamps are formatted in local time, local time is GMT. . . . 2003-02-12 12:57:21.895999 388 UserTrace BIP2638E: MQPUT to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'WBRK_QM': MQCC=0, MQRC=0; node ConfigurationMessageFlow.outputNode'. The node 'ConfigurationMessageFlow.outputNode' attempted to write a message to the specified queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'WBRK_QM'. The MQCC was 0 and the MQRC was 0. No user action required. 2003-02-12 12:57:21.895999 388 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'WBRK_QM'. The WebSphere MQ output node ConfigurationMessageFlow.outputNode' successfully wrote an output message to the specified queue SYSTEM.BROKER.EXECUTIONGROUP.REPLY connected to queue manager WBRK_QM. No user action required. . . . Threads encountered in this trace: 335 388