There are 10 different commands to use with sm_ems. Along with the command, you need to pass arguments. sm_ems commands describes these commands. Where possible in the table, the arguments passed with the command are expressed as attributes from the standard notification. Notification attributes are described in “Adapter Platform and Notifications” on page 99.

With the exception of summarize, all of the sm_ems commands use ClassName, InstanceName, and EventName. These three fields are always required because they uniquely identify a standard notification.

Table 1. sm_ems commands

Command

Description

acknowledge <ClassName> <InstanceName> <EventName>

Changes the notification’s attribute, Acknowledged to TRUE. Attribute values modified using this command argument do not get propagated to Global Manager through the Adapter Platform.

add-audit-log <ClassName> <InstanceName> <EventName> <message>

Adds an entry to the Adapter Platform’s audit log. The entry contains information about the notification as well as a text message (<message>).

assign <ClassName> <InstanceName> <EventName> <Owner>

Changes the notification’s ownership. Attribute values modified using this command argument do not get propagated to Global Manager through the Adapter Platform.

clear <ClassName> <InstanceName> <EventName> <SourceDomainName>

Clears an occurrence of a notification. In order for this command to work, SourceDomainName must match the notification’s attribute.

notify <ClassName> <InstanceName> <EventName> <SourceDomainName> <EventType> <Clear-Mode> [<attribute>=<value> ...]

Creates a notification.

If you use the notify command to create a notification that already exists, the Count attribute is increased by 1 and any attribute which is not explicitly assigned a new value will retain its previous value.

You must use values for each argument through <Clear-Mode>. Clear-Mode indicates how the notification gets cleared. Valid values for Clear-Mode are:

  • source — The source sends a clear.

  • <number> — The number of seconds before the event expires.

  • none — The notification should not expire and the source will not send a clear.

At the end of this command, you have the option of defining other attributes for the command. Optional attributes are: Category, Certainty, ClassDisplayName, ClearOnAcknowledge, EventDisplayName, EventText, Impact, InMaintenance, InstanceDisplayName, Severity, TroubleTicketID, and UserDefined1 through UserDefined10.

In this case, the attribute name must match the standard notification attribute. If you do not explicitly assign values for other attributes, the default attribute values are used. “Adapter Platform and Notifications” on page 99 provides a list of default values.

print <ClassName> <InstanceName> <EventName>

Prints all of the notification’s attributes to stdout.

release <ClassName> <InstanceName> <EventName>

Clears the notification ownership. Attribute values modified using this command argument do not get propagated to Global Manager through the Adapter Platform.

summarize [<Notification_List>]

Prints a summary for a given notification list. If a notification list is not specified, the notification list named Default is used.

unacknowledge <ClassName> <InstanceName> <EventName>

Changes the notification’s attribute, Acknowledged to FALSE. Attribute values modified using this command argument do not get propagated to Global Manager through the Adapter Platform.

update <ClassName> <InstanceName> <EventName> <attribute>=<value> ...

Modifies one or more of a notification’s attributes.