IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

mqsiformatlog command

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 who runs the command.

Supported platforms

Windows
Linux and UNIX systems
z/OS®. Run this command by customizing and submitting BIPFMLG; see Contents of the broker PDSE

Purpose

The mqsiformatlog command interprets an input log file that has been created on any system in a platform-independent code page, utf-8. Use this command 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.

Syntax


>>-mqsiformatlog-- -i --Inputfilename--------------------------->

>--+----------------------+------------------------------------><
   '- -o --Outputfilename-'

Parameters

-i Inputfilename: (Required) The filename of the XML log file that is to be formatted. This file is created by the mqsireadlog command; it is encoded in utf-8.
-o Outputfilename: (Optional) The filename of the file into which the formatted log output is to be written. If this is not specified, the formatted log data is written to stdout.
Output written by this command (to file or stdout) is written in a code page suitable for the current user locale.

Authorization

For information about platform-specific authorizations, see the following topics:

If you have enabled broker administration security, you must also set up the authority detailed in Tasks and authorizations for administration security.

Examples

mqsiformatlog -i trace.xml -o formattrace.log

The following extract shows the output that is 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 
'IB9QMGR': 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 'IB9QMGR'.
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 
'IB9QMGR'. The WebSphere MQ output node ConfigurationMessageFlow.outputNode' 
successfully wrote an output message to the specified queue 
SYSTEM.BROKER.EXECUTIONGROUP.REPLY connected to queue manager IB9QMGR.
No user action required.
.
.
.
Threads encountered in this trace:  335  388

an07270_.htm |

Last updated Friday, 21 July 2017