Service trace is one of two types of optional trace available in WebSphere Event Broker. Service trace is inactive by default, so you must activate it explicitly using a command when you need more information than that provided by the entries in the Event Log or by user trace.
With service trace, you can activate more comprehensive broker tracing, and start tracing for the workbench, Configuration Manager, and User Name Server. 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 workbench.
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 tracing, you cause additional processing for every activity in the component that you are tracing. Large quantities of data are generated by the components. Expect to see some impact in performance 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 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.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an01320_ |