Activate service traces only when you
receive an error message that instructs you to start service trace,
or when directed to do so by your IBM Support
Center
Use the mqsichangetrace command
to start IBM Integration Bus service trace
facilities.
You can select only one broker on each invocation
of the command, but you can activate concurrent traces for more than
one broker by invoking the command more than once.
To limit
the scope of a trace, you must specify the individual broker that
you want to trace.
If the trace cannot be associated with a
specific component, the component name part of the file name is set
to utility; for example, when tracing a command such
as mqsilist, when
no arguments are used.
To
trace the
mqsichangeresourcestats, mqsicreateexecutiongroup,
mqsideleteexecutiongroup,
mqsideploy,
mqsilist, mqsimode,
mqsireloadsecurity,
mqsireportresourcestats, mqsistartmsgflow, and
mqsistopmsgflow commands, use
the
-v parameter. This parameter
takes an argument that is the name of the file to which trace records
are written. For example, the following command outputs trace of the
mqsistartmsgflow command to
the specified file:
mqsistartmsgflow IB9NODE -e eg1 -m simpleflow -v .\trace.txt
If
you want to trace the command executable files themselves, set the
environment variables
MQSI_UTILITY_TRACE and
MQSI_UTILITY_TRACESIZE before you
run the command.
- MQSI_UTILITY_TRACE
- Set this variable to normal for a basic level
of trace, or debug for a fuller trace.
- MQSI_UTILITY_TRACESIZE
- The size, in kilobytes, of the binary trace file. See the -c parameter
of the mqsichangetrace command.
Ensure that you reset these variables when the command
that you are tracing has completed. If you do not do so, all subsequent
commands are also traced, and their performance is therefore degraded.
To enable service trace of your
CMP applications, take one of the
following steps:
- Call the method BrokerProxy.enableAdministrationAPITracing(String
filename).
- Before running your CMP application,
set the environment variable MQSI_CMP_TRACE to the name of the file
to which trace is sent.
You can also use the IBM Integration Explorer to
activate service trace on integration servers and message flows.
To
enable service trace for integration servers or messages flows in the
IBM Integration Explorer:
- In the Navigator view, expand the Integration Nodes folder and right-click the
integration server or message flow with which you want to work.
- Click or to select the level of
service trace that you require.
On z/OS®, enter
the following command:
Last updated Friday, 21 July 2017