Changes in broker startup trace in WMB V8
vivekgrover 120000FG70 Visits (5229)
I always felt it would be easier from a user perspective to have consistent trace commands to capture different types of problems in a product. Starting with WebSphere Message Broker (WMB) V184.108.40.206 and WMB V8, the new trace features in the area of broker startup offer just that. Earlier, the only way to capture a broker and Execution Group startup trace was with the command "mqsiservice".
mqsiservice V81BK -r Trace=debug
mqsiservice V81BK -r exec
where V81BK is the broker name.
Also, a service trace on the broker and Execution Group could be enabled with the command "mqsichangetrace".
mqsichangetrace V81BK -t -b -l debug
mqsichangetrace V81BK -t -e default -l debug -r -c 100000
Starting with WMB V220.127.116.11 and WMB V8, the start up traces for AdminAgent and Execution Group as well as the service trace can be enabled using the command "mqsichangetrace".
mqsichangetrace V81BK -t -b -l debug -r -c 200000
mqsichangetrace V81BK -t -e default -l debug -r -c 200000
where V81BK is the broker name and default is the Execution Group name.
This command can be run even when broker / Execution Group are in stopped state. You can use this in place of the override trace options that were used with the mqsiservice command. The old may also be used though. You must use the old override method when the problem is with broker's configstore tables. Otherwise either of the methods could be used. See the document entitled "WMB broker or execution group startup trace" for the older broker/execution group startup trace instructions.
Along with the above new way of enabling startup traces, an automatic trace turn off option has also been made available using '-m mode' option on the command "mqsichangetrace". This automatically turns off the trace on Execution Group (EG)/Admin Agent (AA) restart or if broker crashes. This is very useful for capturing the abend problems as the trace automatically gets turned off due to AA or EG restart and thus prevents trace overwrites / trace wrap issues.
mqsichangetrace V81BK -t -b -l debug -r -c 200000 -m temp
mqsichangetrace V81BK -t -e default -l debug -r -c 200000 -m temp
The new default trace sizes have also been increased from 4 MB to 100MB. You can use the command "mqsireportrace" to recursively report the trace settings for a broker/Execution Group. This command should be run when the broker is running.
Hope this helps in understanding the new trace features. Let me know if there are any questions.