Service trace

Service trace is one of two types of optional trace that are available in IBM® Integration Bus and provides more information than that provided by the entries that are written to the Event Log or to user trace. Service trace is inactive by default; you must activate it explicitly by using a command.

With service trace, you can activate more comprehensive integration node tracing, and start tracing for the IBM Integration Toolkit. You can also trace the execution of all the commands described in Commands, including the trace commands themselves. Use the mqsichangetrace command to work with service trace; you cannot use the IBM Integration Toolkit.

Activate service trace only when you receive an error message that instructs you to, or when directed to do so by your IBM Support Center.

When you activate service trace, you cause additional processing for every activity in the component that you are tracing. Large quantities of data are generated by the components. Expect performance to be affected while service trace is active. You can limit this additional processing by being selective about what you trace, and by restricting the time during which trace is active.

The location of the trace logs depends on your environment:

Windows: If you have set the work path by using the -w parameter of the mqsicreatebroker command, the location is workpath\log.; If you have not specified the integration node work path, the default location is %PROGRAMDATA%\IBM\MQSI\Common\log where %PROGRAMDATA% is the environment variable that defines the system working directory. The default directory depends on the operating system.
Linux® and UNIX: /var/mqsi/common/log
z/OS®: /component_filesystem/log

The directory to which the service trace logs are written must be able to hold all the logs for that computer. You might want to place it on a separate file system, if allowed by your system operator.