IBM E027SLL-H Troubleshooting Guide - Page 68

To trace the 2way translator, set the trace level to (UNIT: KDY ALL) (UNIT: KHD_XA ALL) in the Summarization and Pruning Agent environment file for KBB_RAS1. Setting the trace option for the tacmd commands For Windows systems, manually edit the KUIENV file in the CANDLEHOME directory with the standard KBB_RAS1 statement to include the following: KBB_RAS1=ERROR(UNIT:ksh all) (UNIT:kui all) . On UNIX systems, manually edit the $CANDLEHOME/bin/tacmd shell script to add a line like the following example: KBB_RAS1=ERROR(UNIT:ksh all) (UNIT:kui all) In order to debug KT1 as well, edit the line to be like the following example: KBB_RAS1=ERROR(UNIT:ksh all) (UNIT:kui all) (UNIT:kt1 all) Setting the trace option for the IBM Tivoli Monitoring upgrade toolkit Table 4. Setting the trace option for the Tivoli Monitoring upgrade toolkit Trace option Instructions Endpoint tracing Run the following command to set log_threshold=3 or higher on an endpoint and enable endpoint tracing: wep ep set_config log_threshold=3 Tracing in a test environment. Traces are written to lcfd.log on the endpoint in $LCF_DATDIR. A Boolean value of TRUE or FALSE default. The default is FALSE. Run the following command from a Tivoli Management Environment command prompt to enable tracing:idlcall oid _set_debug TRUE where: oid Specifies the object ID of the Upgrade Manager object. Run the wlookup Framework command to locate the Upgrade Manager object ID in the Tivoli Management Environment: wlookup -a | grep Upgrade OS Agent tracing Note: Setting the trace value to TRUE sets all Upgrade Toolkit tools to TRUE, affecting all users running Upgrade Toolkit tools. A trace file named trace_tool_timestamp.log is created in the $DBDIR/AMX/trace/ directory in XML format, with tool being 'witmscantmr', 'witmassess', and 'witmupgrade', and timestamp a time stamp that includes data and time of execution. Each record in this log contains a time stamp and message. Additionally, these tools inherit Framework FFTC mechanisms such as wtrace and odstat for transaction and method stack traces. See the Tivoli management Framework documentation for more information about the commands. OS Agent tracing is enabled at a minimum level by default. Agent tracing levels can be adjusted with agent specific settings. Logs are stored in install_dir\installITM\ on Windows agents or install_dir/logs/ on UNIX-based systems agents. These logs follow the RAS1 log format. 50 IBM Tivoli Monitoring: Troubleshooting Guide