Service trace is used to get detailed information about your environment for use 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.
mqsistartmsgflow IB9NODE -e eg1 -m simpleflow -v .\trace.txt
You can also use the IBM Integration Explorer to activate service trace on integration servers and message flows.
mqsichangetrace BrokerA -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)
F MQPIBRK,ct t=yes, b=yes, l=debug
mqsichangetrace BrokerA -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
F MQPIBRK,ct t=yes, l=debug, m=fast, c=20000, r=yes