IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Stopping user trace

Use user trace for debugging your applications; you can trace brokers, integration servers, and deployed message flows. Stop user trace facilities by using the mqsichangetrace command or the IBM® Integration Explorer.

Use the mqsichangetrace command with a trace level of none to stop an active trace. This action 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 integration server test, an active trace on another integration server continues.

You can also stop an active trace for integration servers or assigned message flows by using the IBM Integration Explorer. If you redeploy a component from the IBM Integration Explorer, trace for that component is returned to its default setting of none.

Example: stopping user trace on the default integration server

To stop the trace started by the command shown in Starting user trace, on distributed systems, enter the following command:

mqsichangetrace IB9NODE -u -e default -l none

where:

-u specifies user trace
-e specifies the integration server (in this case, the default integration server)
-l specifies the level of trace (in this case, none)

On z/OS®, enter the following command:

F MQP1BRK,ct u=yes, e='default', l=none

Example: stopping user trace on a message flow from the IBM Integration Explorer

You can stop user trace on individual message flows, or select an integration server and stop user trace on all the message flows in the integration server.

To stop trace for one of your message flows from the IBM Integration Explorer:

In the Navigator view, expand the Integration Nodes folder and right-click the message flow with which you want to work.
Click User trace > None.

au14330_.htm |

Last updated Friday, 21 July 2017