Starting service trace

Service trace is used to get detailed information about your environment for use by your IBM® Support Center.

About this task

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 integration node on each invocation of the command, but you can activate concurrent traces for more than one integration node by invoking the command more than once.

To limit the scope of a trace, you must specify the individual integration node 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 IBNODE -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 custom integration applications, take one of the following steps:

Call the method BrokerProxy.enableAdministrationAPITracing(String filename).
Before running your custom integration application, set the environment variable MQSI_CMP_TRACE to the name of the file to which trace is sent.

Example: starting service trace for the integration node

About this task

To start debug level service tracing for the IBNODE on distributed systems, enter the following command:

mqsichangetrace IBNODE -t -b -l debug

where:

-t specifies service trace
-b specifies that trace for the agent subcomponent of the specified component
is to be started
-l specifies the level of trace (in this case, debug)

On z/OS®, enter the following command:

F MQPIBRK,ct t=yes, b=yes, l=debug

Example: starting service trace for an integration server

About this task

To start debug level service tracing for an integration server IS1 on IBNODE on distributed systems, enter the following command:

mqsichangetrace IBNODE  -t -e IS1 -l debug -m fast -c 200000 -r

where:

-t specifies service trace
-l specifies the level of trace (in this case, debug)
-m specifies the way trace information is to be buffered (in this case, fast)
-c specifies the size of the trace file in KB (in this case, 200000)
-r specifies that the trace file is reset

On z/OS, enter the following command:

F MQPIBRK,ct t=yes, l=debug, m=fast, c=20000, r=yes