Dynamic modification of trace settings

IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agentless OS Monitor User's Guides > Agentless Monitoring for AIX User's Guide > Troubleshooting > Trace logging IBM Tivoli Monitoring, Version 6.3

Dynamic modification of trace settings

You can dynamically modify the trace settings for an IBM Tivoli Monitoring component, such as, Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, most monitoring agents, and other components. You can access these components, except for a few monitoring agents, from the tracing utility.
Dynamic modification of the trace settings is the most efficient method, because you can do it without restarting the component. Settings take effect immediately. Modifications by this method are not persistent.
When the component is restarted, the trace settings are read again from the .env file. Dynamically modifying these settings does not change the settings in the .env files. To modify these trace settings permanently, modify them in the .env files.

ras1

Run this command to modify the trace settings for a Tivoli Monitoring component.
The syntax is as follows:
ras1 set|list (UNIT|COMP: class_name ANY|ALL|Detail|ERROR|Flow|INPUT|Metrics|OUTPUT|STATE) 
{(UNIT|COMP: class_name ANY|ALL|Detail|ERROR|Flow|INPUT|Metrics|OUTPUT|STATE)}
You can specify more than one component class to which to apply the trace settings.

Command options

set

Turns on or off tracing depending upon the value of its parameters. If the parameter is ANY, it turns it off. All other parameters turn on tracing based on the specified type or level.

list

Displays the default level and type of tracing that is set by default.

Parameters

The parameters that determine the component classes to which to apply the trace settings are as follows:

COMP: class_name

Modifies the trace setting for the name of the component class, as specified by class_name , for example, COMP:KDH. The output contains trace for the specified class.

UNIT: class_name

Modifies the trace setting for any unit that starts with the specified class_name value, for example, UNIT: kra. The output contains trace for any unit that begins with the specified filter pattern.

The parameters that determine the trace level and type are as follows:

ALL

Displays all trace levels, including every trace point defined for the component. This setting might result in a large amount of trace, so specify other parameters to exclude unwanted trace. You might require the ALL parameter to isolate a problem, which is the equivalent to setting "Error Detail Flow State Input Output Metrics".

ANY

Turns off tracing.

Detail

Displays detailed information about each function.
When entered with the list option, the trace is tagged with Det.

ERROR

Logs internal error conditions.
When entered with the list option, the trace is tagged with ER. The output can also be tagged with EVERYE+EVERYU+ER.

Flow

Displays control flow data for each function entry and exit.
When entered with the list option, the trace is tagged with Fl.

INPUT

Displays input data for each function.
When entered with the list option, the trace is tagged with IN.

Metrics

Displays metrics on each function.
When entered with the list option, the trace is tagged with ME.

OUTPUT

Displays output data for each function.
When entered with the list option, the trace is tagged with OUT.

State

Displays the status for each function.
When entered with the list option, the trace is tagged with St.

Example
If you enter ras1 set (COMP:KDH ALL) (COMP:ACF1 ALL) (COMP:KDE ALL), the trace utility turns on all levels of tracing for all the files and functions for which KDH, ACF1, and KDE are the classes.
kbbcre1.c, 400, May 29 2007, 12:54:43, 1.1, * 
kbbcrn1.c, 400, May 29 2007, 12:54:42, 1.1, * 
kdhb1de.c, 400, May 29 2007, 12:59:34, 1.1, KDH 
kdh0med.c, 400, May 29 2007, 12:59:24, 1.1, KDH 
kdhsrej.c, 400, May 29 2007, 13:00:06, 1.5, KDH 
kdhb1fh.c, 400, May 29 2007, 12:59:33, 1.1, KDH 
kdhb1oe.c, 400, May 29 2007, 12:59:38, 1.2, KDH
kdhs1ns.c, 400, May 29 2007, 13:00:08, 1.3, KDH
kbbacdl.c, 400, May 29 2007, 12:54:27, 1.2, ACF1
kbbaclc.c, 400, May 29 2007, 12:54:27, 1.4, ACF1 
kbbac1i.c, 400, May 29 2007, 12:54:28, 1.11, ACF1 
vkdhsfcn.c, 400, May 29 2007, 13:00:11, 1.1, KDH 
kdhserq.c, 400, May 29 2007, 12:59:53, 1.1, KDH 
kdhb1pr.c, 400, May 29 2007, 12:59:39, 1.1, KDH
kdhsgnh.c, 400, May 29 2007, 12:59:49, 1.1, KDH
kdh0uts.c, 400, May 29 2007, 12:59:23, 1.1, KDH
kdhsrsp.c, 400, May 29 2007, 13:00:13, 1.2, KDH
kdhs1rp.c, 400, May 29 2007, 13:00:12, 1.1, KDH
kdhscsv.c, 400, May 29 2007, 12:59:58, 1.9, KDH
kdebbac.c, 400, May 29 2007, 12:56:50, 1.10, KDE 
...
Turning on tracing
To use the tracing utility, use a local logon credential for the computer. This tracing method uses the IBM Tivoli Monitoring Service Console. Access the Service Console by using a web browser.

Turning off tracing
You can use the IBM Tivoli Monitoring Service Console to run the ras1 command and dynamically turn off tracing.

Parent topic:
Trace logging

+
Search Tips | Advanced Search