IBM Tivoli Monitoring, Version 6.3

tacmd listtrace

Description

Use the listtrace command to query the RAS1 logging level on a remote managed system. You must log in by using the tacmd login command before running the tacmd listtrace command. Each tacmd listtrace command returns either the current value of the RAS1 trace variable or a status message providing diagnostic information, if an error occurred.

Note that all ITM processes in the RAS1 command flow must be at ITM v6.2.3 Fix Pack 2 (or higher), as only those releases support the RAS1 Dynamic Trace Facility. For example, if a tacmd listtrace request must travel from hub to remote monitoring server to agent, all three components must be at ITM v6.2.3 Fix Pack 2 (or higher) or the request will fail.

CLI syntax

tacmd listtrace
{-m|--system} SYSTEM
{-p|--property} PROPERTY

where:

-m|--system: Specifies to which managed system to send the listtrace command.
-p|--property: Identifies the RAS1 trace property to query. Valid values include KBB_RAS1, KDC_DEBUG, KDE_DEBUG, KDH_DEBUG, KLX_DEBUG, and KBS_DEBUG. Note that KLX_DEBUG is only active on z/OS and Windows platforms. KBS_DEBUG is only active if 1) it has been set as an environment variable on the managed system, or 2) it was dynamically activated with a previous tacmd settrace command.

CLI example

This example displays the current KBB_RAS1 value of an agent on SystemA:

tacmd listtrace -m SystemA:Agent1 -p KBB_RAS1

This example displays whether debug tracing of the KDH component is active on the HUB.

tacmd listtrace -m *HUB -p KDH_DEBUG

Note: A hub monitoring system can be specified using either its CMS_NODEID value or as *HUB.

Return values

See Table 1.

Related commands

tacmd settrace

Return to Table 1.

Feedback