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

Switching Trace nodes on and off

Use the mqsichangetrace command or the IBM® Integration Explorer to switch Trace nodes on and off.

When an integration server is created, or a message flow is deployed, its Trace node switch is set to on by default. Integration servers and message flows that you have migrated from a previous version are also handled in this way. The message flow level Trace node switch setting is not changed on redeployment. You can significantly improve the performance of a flow that includes Trace nodes by switching Trace nodes off.

Restriction: If you switch off Trace nodes in a flow that was migrated from a version earlier than 6.1, you can no longer revert that flow to its earlier state.

If the Trace node setting for an integration server is off, all Trace nodes in its flows are disabled. You can change the settings for Trace nodes in individual message flows; the settings are applied when you turn on Trace nodes for the integration server. If the Trace node setting for an integration server is on, the Trace node switch setting of each message flow determines the effective settings. Use the mqsireporttrace command to check the settings for message flows and integration servers.

Example: switching off Trace nodes for an integration server on distributed systems, using the command line

To disable the Trace node switch settings of all message flows in an integration server of a broker called IB9NODE, (that is, stop all the Trace nodes in any of the message flows deployed to the integration server from executing), enter the following command:

mqsichangetrace IB9NODE –n off -e default

In this example, -n off switches off Trace nodes in the default integration server (-e default).

All Trace nodes are switched off, even if the message flow that contains them has its Trace node switch set to on.

Example: switching off Trace nodes for an integration server on z/OS® systems, using the command line

To disable the Trace node switch settings of all message flows in an integration server of a broker called MQP1BRK, (that is, stop all the Trace nodes in any of the message flows deployed to the integration server from executing), enter the following command:

F MQP1BRK,ct n='off', e='default'

In this example, n='off' switches off Trace nodes in the default integration server (e='default').

All Trace nodes are switched off, even if the message flow that contains them has its Trace node switch set to on.

Example: switching off Trace nodes for a message flow on distributed systems, using the command line

Trace nodes for the default integration server in broker IB9NODE are switched on. You want to turn off Trace nodes for the myFlow message flow.

Enter the following command:

mqsichangetrace IB9NODE -n off -e default -f myFlow

Example: switching on Trace nodes for a message flow and an integration server on distributed systems, using the command line

Trace nodes for the default integration server in broker IB9NODE are switched off. You want to turn on Trace nodes for the myFlow message flow, then turn on Trace nodes for the integration server.

To turn on Trace nodes for the message flow, enter the following command:
```
mqsichangetrace IB9NODE -n on -e default -f myFlow
```
Trace nodes for the myFlow message flow are turned on, but this setting is not applied until you turn on trace nodes for the integration server.
To turn on Trace nodes for the integration server, enter the following command:
```
mqsichangetrace IB9NODE –n on -e default
```
Trace nodes are turned on for the default integration server. Within that integration server, Trace nodes are enabled in all message flows that have Trace nodes turned on, including the myFlow message flow.

Example: switching off Trace nodes for a message flow on z/OS systems, using the command line

Trace nodes for the default integration server in broker MQP1BRK are switched on. You want to turn off Trace nodes for one of the message flows (myFlow).

Enter the following command:

F MQP1BRK,ct n='off', e='default', f='myFlow'

Example: switching on Trace nodes for an integration server, using the IBM Integration Explorer

Trace nodes are enabled by default. If you have switched them off, follow these steps to enable Trace nodes for an integration server from the IBM Integration Explorer:

In the Navigator view, expand the Integration Nodes folder and right-click the integration server with which you want to work.
Click Trace Nodes All Flows > Enable. An alert saying Trace nodes are switched on is displayed in the Alert Viewer. The Trace node switch setting of each message flow determines the effective settings.

Example: switching on Trace nodes for a message flow, using the IBM Integration Explorer

Follow these steps to enable Trace nodes 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 Trace Nodes > Enable An alert is displayed in the Alert Viewer.

au60100_.htm |

Last updated Friday, 21 July 2017