wtdumprl command

The wtdumprl command is used to display all received events and their disposition, whether they are processed or get a parsing failed status. When parsing fails, it means that either the class is not defined or there is an unknown slot (field) or an unparsable slot.
The wtdumptr command is used to display the completion of the action invoked from the TEC rules for an event. For example, the completion code of invoking the event enablement exits.

To see how the message arrived and in what format, type in wtdumprl on the TEC server. For example:

wtdumprl -o DESC | more

or

wtdumprl -t 'May 16 10:00:00 2006' -e 'May 10 10:30:00 2006' > tec.out

You can also create event files
From a bash or UNIX shell command line, enter the following command. The directory argument specifies the directory to write the event folders (which contain event files), events_list file, and time_list file.
wtdumprl | $BINDIR/TME/TEC/contrib/ParseEvents.pl -d directory
The event files are generated in a directory structure like the following figure. For this example, the preceding command was issued with the -d /test3 argument.

Reference

wtdumprl

Generates a report of received events from the reception log.

Syntax

wtdumprl [-f file] [-t start_time] [-e end_time] [-o ASC | DESC] [-m number]

Description

The wtdumprl command generates a report of events received by the event server. The reception log maintains a list of these events in the database. The default action is for events to be listed in the order they occurred. However, the most recent event can be listed first by using the -o flag.

If wtdumprl is run from a node other than the Tivoli Enterprise Console server, it uses the time from the local system to determine which events to display, and this might cause unexpected behavior.

For example, if the time on the node is 9:00 and the Tivoli Enterprise Console server is 9:30, a wtdumprl run from the node displays every event in the database except for those occurring during the 30 minutes specified. The same command run on the Tivoli Enterprise Console server would display the entire database.

Authorization

senior, RIM_view

Options

-e end_time

Lists events that were received prior to the specified date and time. The end_time parameter must be a date in the format of "Mon dd hh:mm:ss yyyy". If this flag is omitted, the command uses the current time as the end time.

-f file

Writes output to the specified file.

-m number

Specifies the maximum number of events to record in the report. If the number of events in the log exceeds the specified value, the command omits entries from the end of the report. For example, if the report is displayed in ascending order, the most recent database entries are not included in the report.

-o ASC | DESC

Sets the order in which events are listed. The possible values are:

ASC: Lists the oldest log entry first. This is the default value.
DESC: Lists the most recent log entry first.

-t start_time

Lists events that were received after the specified date and time. The start_time parameter must be a date in the format of "Mon dd hh:mm:ss yyyy".

Examples

The following example generates a report that includes all events received between 7 PM on March 9, 1999 and 9 AM on March 12, 1999:

wtdumprl -t "MAR 09 19:00:00 1999" -e "MAR 12 09:00:00 1999"

Copyright © 1996-2008 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. Submit comments This document is an industrial compilation designed and created exclusively for educational use and is placed under the copyright of the Open Content License(OPL). Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

Standard disclaimer: The statements, views and opinions presented on this web page are those of the author and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: March 15, 2008