Use the mqsichangetrace with a trace level of none to
stop an active trace. This stops the trace activity for
the component that you specify on the command. It does not affect active traces
on other components. For example, if you stop tracing on the execution group test,
an active trace on another execution group continues.
On Windows, for execution groups or assigned
message flows, you can also use the workbench to
stop an active trace.
If you redeploy a component from the workbench,
trace for that component is returned to its default setting of none.
Example: stopping user trace on the default execution group
To stop the trace started by the command shown in Starting user trace, on distributed platforms, enter the command mqsichangetraceWBRK_BROKER -u
-e default -l none where:
-u
specifies user trace
-e
specifies the execution group (in this case, the default execution group)
-l
specifies the level of trace (in this case, none)
On z/OS, enter
the command F MQP1BRK,ct u=yes, e='default', l=none
Example: stopping user trace on a message flow from the workbench
To stop trace for one of your message flows from the workbench:
Switch to the Broker
Administration perspective.
In the Domains view, right-click on the message flow that for which
you want to stop trace.