Start of change
IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


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 trace 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 App Connect Enterprise service trace facilities.

You can select only one integration node or server on each invocation of the command, but you can activate concurrent traces for more than one by invoking the command more than once.

To limit the scope of a trace, you must specify the individual integration node or server that you want to trace.

Starting service trace for a command

About this task

To trace an IBM App Connect Enterprise command, use the --trace parameter on the command to specify the file to which trace records will be written. For example, the following command outputs a trace of the mqsilist command to the specified file:
mqsilist myIntegrationNode --trace c:\tmp\listtrace.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 will be degraded.

Starting service trace for an integration node

About this task

To start a debug-level service trace for the integration node INODE, enter the following command:
mqsichangetrace INODE -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)

Starting service trace for an integration server that is managed by an integration node

About this task

To start a debug-level service trace for an integration server IS1 on INODE, enter the following command:
mqsichangetrace INODE  -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

Starting service trace for an independent integration server

About this task


au14270_.htm | Last updated 2018-11-02 14:46:07
End of change