Using The Uagent Application; Pdcollect Tool - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Using the UAGENT application

The UAGENT application is a diagnostic tool to help solve problems you might
experience with the universal agent. Every universal agent data provider
automatically activates an application called UAGENT, which includes the DPLOG
and ACTION workspaces.
DPLOG
ACTION workspace

pdcollect tool

Use the pdcollect tool to collect the most commonly used information from a
system. Technicians in IBM Software Support use this information to investigate a
problem.
The pdcollect tool is used to gather log files, configuration information, version
information, and other information to help solve a problem. You can also use the
tool to manage the size of trace data repositories.
The DPLOG is a pure event table in that it maintains only the most recent
100 rows, unless overridden by the KUMA_MAX_EVENT_ENTRIES
environment variable. The DPLOG contains informational and error
messages about the status of a data provider that indicate:
v If a metafile was validated successfully.
v If a metafile failed validation (which means the application will not
come online).
v If a data source was available at startup
v Which console ports and socket listening ports were used or unavailable.
v When monitoring started and stopped for a data source.
v When monitoring switched from one file to another.
v When an API or socket client program connected and disconnected.
The DPLOG also records other actions including metafile refreshes. The
two most common universal agent problem symptoms are:
v One or more managed systems do not come online.
v The managed systems are online but the workspaces are empty.
Use the UAGENT application workspaces as one of the first tools to
diagnose a universal agent problem. You might find the solutions for both
problems in the appropriate DPLOG. The ODBC data provider also
includes a DPLOG message indicating when monitoring started for every
attribute group listed in every ODBC metafile.
Whenever a Take Action command is issued or a Reflex Action fires, an
entry is added to the ACTION workspace. The Action table is keyed and
ActionID is the Key attribute. The Action table rows have a time-to-live
value of 30 minutes. Unlike the DPLOG which is data provider-specific,
the ACTION table is shared by all data providers. If you run multiple data
providers, the ACTION workspace under every UAGENT application
contains the same rows.
The Action_Result can indicate what happened to a particular Take Action
command. For example, if universal agent reflex actions fire faster than one
per second, the ACTION workspace temporarily stops recording the
results. Recording resumes after several minutes if the action rate slows
down.
59
Chapter 4. Tools