You can initiate, modify, or terminate user tracing for a broker, or initiate, modify, or terminate service tracing for a broker, a Configuration Manager, or the User Name Server (identified by component name). You cannot use this command to initiate service tracing for the workbench.
On Windows platforms, Linux, and UNIX systems, you can also start and stop tracing activity for execution groups and message flows using the facilities of the workbench. See User trace for more information.
On z/OS, you can also start, modify, or stop a trace using the console commands or using the facilities of the workbench.
If you specify a broker, or any of its resources (execution group or message flow), you must have deployed them before you can start trace.
The trace output generated by these commands is written to trace files in the log subdirectory. When you have completed the work you want to trace, use mqsireadlog to retrieve the log as an XML format file. Use either mqsiformatlog (to produce a formatted file) or an XML browser to view the XML records.
When you set tracing on, you cause additional processing to be executed for every activity in the component you are tracing. You must expect to see some impact on performance when trace is active.
If you want to trace the command processes themselves, set the environment variables MQSI_UTILITY_TRACE and MQSI_UTILITY_TRACESIZE before you initiate trace.
Ensure that you reset these variables when tracing for the selected command is complete. If you do not do so, all subsequent commands are also traced, and their performance degraded.
Key words workbench and utility are
reserved and must not be used as a component name.
On z/OS, this name is case sensitive and you should include the names in single quotes if they contain mixed case characters.
On z/OS, this name is case sensitive and you should include the names in single quotes if they contain mixed case characters.
This option is only valid if you have specified an execution group (flag -e).
Each component is created with a default value of none. If you do not specify this parameter, the current value is unchanged. Once you successfully change this value, it is persistent.
This is valid for all components.
Each component starts with a default value of safe. If you do not specify this parameter, the current value is unchanged.
On HP-UX you are recommended to set this value below 500 MB.
However you intend to retrieve the trace file, you are recommended to keep its size as small as possible, either by using a low value for this parameter or by using the reset (-r) option on this command to clear the trace log. The benefit of adopting this approach is that the formatting process (mqsiformatlog) is much faster and requires less resource to carry out its task.
If you change the trace size, the new value is persistent over a restart of the broker or User Name Server.
Use these options only when directed to do so by your IBM Support Center or by a BIPxxxx message.
Windows platforms, Linux, and UNIX systems:
mqsichangetrace WBRK_BROKER -u -e default -l normal -c 5000
mqsichangetrace WBRK_BROKER -u -e default -m fast
mqsichangetrace WBRK_BROKER -t -b -m -l normal
z/OS:
F MQP1BRK,ct u=yes,e='default',l=normal,c=5000and in the PDSE member BIPJLOG, set the option for mqsireadlog to
-u -e default
F MQP1BRK,ct u=yes,e='default',f='f1',m=fastand in the PDSE member BIPJLOG, set the option for mqsireadlog to
-t -e default -f f1-
F MQP1BRK,ct t=yes,b=yes,m=fast,l=debugand in the PDSE member BIPJLOG, set the option for mqsireadlog to
-t -b agent
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an07260_ |