Use the mqsichangetrace command to start WebSphere Message Broker 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.
You must specify the individual component that you want to trace; for example the broker, Configuration Manager, or User Name Server, to limit the scope of a trace.
If you want to trace the command executable files themselves, set the environment variables MQSI_UTILITY_TRACE and MQSI_UTILITY_TRACESIZE before you initiate trace. Ensure that you reset these variables when the command that you are tracing has completed. If you do not do so, all subsequent commands are also traced, and their performance is therefore degraded.
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.
In order to trace the mqsideploy, mqsistartmsgflow, mqsistopmsgflow, mqsicreateexecutiongroup, and mqsideleteexecutiongroup commands, use the -v parameter. This takes an argument that is the name of the file to which trace will be written.
mqsichangetrace UserNameServer -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 MQPIUNS,ct t=yes, b=yes, l=debug