There are two kind of traces we use to troubleshoot any issue in IIB/ACE -
User Trace:
This trace is useful for developers for debugging and it generate low level of trace capture.
Below are the steps to generate this and analyze -
1. Start trace:
mqsichangetrace ACENODE -e EGName -u -l debug -r -c 200000
2. Re-create the runtime behavior.
3. Stop trace:
mqsichangetrace ACENODE -e EGName -u -l none
4. Verify trace status
mqsireporttrace ACENODE -e EGName
Service trace -
This is detailed trace and captures everything required to analyze the issue and required when you are working with IBM support to resolve a particular issue.
1. Start/enable trace
mqsichangetrace ACENode -e EG_Name -t -l debugTree -r -c 200000
2. Recreate the issue
3. Stop/disable the trace
mqsichangetrace ACENode -e EG_Name -t -l none
4. Verify the trace status
mqsireporttrace ACENode -e EG_Name
The generated log could be found under this dir/location - /var/mqsi/common/log
No comments:
Post a Comment