User Level Trace : User trace provides more information than that provided by the entries that are written to the logs. Typically, you use user trace for debugging your applications, as it can trace brokers, execution groups, and deployed message flows.
1. Start trace .
- mqsichangetrace <brokername> -u -e <egroup> -l debug -r -c 50000
<brokername> is the name of your broker
<egroup> is the name of your execution group
2. Put a message on the input node queue to cause the failure to occur.
3. Stop trace.
mqsichangetrace <brokername> -u -e <egroup> -l none
You can also stop tracing, by going to Operations tab, and right click Message Flow, and click Stop Trace
4. Retrieve the trace log for the specified component.
- mqsireadlog <brokername> -u -e <egroup> -f -o flowtrace.xml
5. Format XML tracefile.
- mqsiformatlog -i flowtrace.xml -o userflowtrace.txt
The userflowtrace.txt will be in the current working directory.
Service Level Trace : Service trace provides more detailed information than that provided by the entries that are written to the Syslogs, Event Logs, Trace Node Outputs, or User Trace. Typically, IBM support uses service trace for debugging problems as it can trace internal calls in addition to the brokers, execution groups, and deployed message flows
1. Start trace.
mqsichangetrace <brokername> -t -e <egroup> -l debug -r -c 100000
2. Put a message on the queue to cause the failure to occur.
3. Stop trace.
mqsichangetrace <brokername> -t -e <egroup> -l none
4. Retrieve the trace log for the specified component.
mqsireadlog <brokername> -t -e <egroup> -f -o flowtrace.xml
5. Format the XML trace file.
mqsiformatlog -i flowtrace.xml -o serviceflowtrace.txt
The serviceflowtrace.txt will be in the current working directory.
