Hitachi

JP1 Version 12 JP1/Performance Management Reference


jpctool alarm import

Organization of this page

Format

jpctool alarm import    -f alarm-definition-file-name
                       [-y|-n]
                       [-wait number-of-seconds]

Function

The jpctool alarm import command imports alarm definitions from the specified file, and defines and updates an alarm table and alarms.

Definition information is imported in units of alarms. If the alarm definition file contains definitions of multiple alarms and importation of one alarm's definition terminates abnormally, import processing continues for the next alarm definition. If multiple errors occur while the command is importing multiple alarm definitions, the return code set by the command is for the last error that occurred.

Before importing definition information, this command checks the syntax of the alarm definition file and the validity of the definition information. If there is an error in the syntax of the alarm definition file or the validity of the definition information, the command displays an error message containing the row number in the file and the nature of the error only for the first error that occurred.

The following table lists and describes the cause and nature of the errors that can be displayed in the error message:

Table 3‒47: Causes of errors displayed in error messages and nature of errors

Cause of error

Nature of error

The specified entry is invalid

A specified label name or section name is invalid.

The specified value is invalid

A specified value is invalid.

The syntax is invalid

There is a syntax error in the alarm definition file.

The entry (label-name-or-section-name) is not specified

The indicated required label or section is missing.

The specified product is invalid

A specified product ID or data model version is invalid.

The specified field is not defined

A specified record name or field name is not supported by the PFM - Agent or PFM - RM with the specified product ID.

The specified report is not defined

A specified report is not defined in the PFM - Agent or PFM - RM with the specified product ID.

The specified Action Handler is not defined

The specified action handler is missing.

The specified Action Handler does not have capability

The specified action handler has not been set to execute the specified action.

A Character-code is invalid

The specified character encoding is invalid.

The specified definition is too many

The number of alarm definitions exceeds the permitted maximum.

Total length of Abnormal condition definition is too long

The length of an abnormal condition statement in the alarm definition exceeds the permitted maximum length.

Total length of Warning condition definition is too long

The length of a warning condition statement in the alarm definition exceeds the permitted maximum length.

Hosts that can execute the command

PFM - Manager

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

Installation directory

In Windows:
installation-folder\tools\
In UNIX:
/opt/jp1pc/tools/

Arguments

-f alarm-definition-file-name

Specifies the name of the alarm definition file that is to be imported. The file name can be expressed as a relative path or an absolute path.

The string you specify can have double-byte characters, single-byte alphanumeric characters, single-byte spaces, and the following single-byte symbols:

% - ( ) _ . @ [ ]

If the value contains a space, enclose the entire value in double quotation marks ("). If the value contains a defined symbol, specify an escape character if necessary.

-y|-n

Specifies whether or not the existing definition information is to be updated forcibly if an alarm definition to be imported already exists.

When -y is specified, the command forcibly updates the existing alarm definition.

When -n is specified, the command skips update processing.

When this option is omitted, the command displays a confirmation message asking whether or not an existing alarm definition is to be overwritten.

-wait number-of-seconds

Specifies the maximum wait period (in seconds) applied when a command that cannot be executed with this command is running. When the setting to suspend execution of wait alarm commands (Alarm Command Wait Mode) is enabled in the startup information file (jpccomm.ini), if you want to specify a wait period (in seconds) separately from the wait period specified in the jpccomm.ini file, specify a value in the range from 1 to 3,600 for this option.

If you omit the option, this command runs with the wait period (in seconds) specified in the jpccomm.ini file.

For details on the commands that cannot be executed with this command, see Commands that cannot be executed with alarm commands. For details on the jpccomm.ini file and Alarm Command Wait Mode, see Startup information file (jpccomm.ini).

Alarm definition file format

List of settings values

  • Alarm Definition File Version label

    Specifies the version of the alarm definition file syntax. The specified location is at the beginning of the file.

Table 3‒48: Alarm Definition File Version label

Type

Description

Description

Indicates the version of the alarm definition file syntax.

Specifiable value

0001 or 0002 can be specified.

  • When 0001 is specified

    The file can be imported from all versions of PFM - Manager.

  • When 0002 is specified

    The file can be imported from PFM - Manager 10-10 or later. Also, you can define the alarm for notification of state changes for each instance.

Omissible

No

  • Alarm Definition File Code label

    The encoding for the alarm definition file is specified immediately after the Alarm Definition File Version label.

Table 3‒49: Alarm Definition File Code label

Type

Description

Description

Indicates the encoding for the alarm definition file.

Specifiable value

  • Shift_JIS

    Specify this value if the file is created with double-byte SJIS characters or single-byte characters (7-bit ASCII characters).

  • EUC-JP

    Specify this value if the file is created with double-byte EUC characters or single-byte characters (7-bit ASCII characters).

  • UTF-8

    Specify this value if the file is created with double-byte UTF-8 characters or single-byte characters (7-bit ASCII characters).

  • C

    Specified only when the file was created with single-byte characters (7bit ASCII characters).

  • GB18030

    Specify this value if the file is created with double-byte GB18030 characters or single-byte characters (7-bit ASCII characters).

Omissible

No

  • Alarm Data section

    Specifies the definition for a single alarm. When multiple alarms are defined, an Alarm Data section is created for each alarm definition. The Alarm Data section cannot be omitted.

    The subsections that can be specified within the Alarm Data section are as follows.

Table 3‒50: Alarm Data section

Subsection name

Description

Optional

General

Sets basic information such as alarm name.

No

Advanced Setting

Sets the alarm type and options.

Yes

Check Value Exist

Sets the monitored values for alarms that monitor the existence of a value.

Yes (depending on the alarm definition)

Alarm Condition Expressions

Sets an alarm conditional expression for alarms other than those that monitor the existence of a value.

Yes (depending on the alarm definition)

Actions

Sets the executed action and displayed report for an alarm.

Yes

Action Definition E-mail

Specifies the settings for when an email is executed by an alarm.

Yes (depending on the alarm definition)

Action Definition Command

Specifies the settings for when a command is executed by an alarm.

Yes (depending on the alarm definition)

Action Definition JP1 Event

Specifies the settings for when a JP1 event is executed by an alarm.

Yes (depending on the alarm definition)

Legend:

Yes: Can be omitted.

No: Cannot be omitted.

  • General subsection

    Specifies basic alarm information (such as the alarm name and message text). This subsection cannot be omitted.

    The labels that can be specified for this subsection are as follows.

Table 3‒51: Product label

Type

Description

Description

Indicates the product and data model version for the alarm.

Specifiable value

<product-ID><data-model-version>

  • product-ID

    Specifies the product ID of the agent for which the alarm is to be defined, in uppercase letters.

  • data-model-version

    Specifies the version and revision in decimal notation, joined by periods (.).

Omissible

No

Table 3‒52: Alarm Table Name label

Type

Description

Description

Indicates the alarm table name.

Specifiable value

A string that is 1 to 64 bytes long and consists of double-byte and/or single-byte characters.

Any spaces after equals signs (=) and before line returns are ignored.

Names starting with PFM (case-insensitive) cannot be specified.

Omissible

No

Table 3‒53: Alarm Name label

Type

Description

Description

Indicates the alarm name.

Specifiable value

A string that is 1 to 20 bytes long and consists of double-byte and/or single-byte characters.

Any spaces after equals signs (=) and before line returns are ignored.

Omissible

No

Table 3‒54: Message Text label

Type

Description

Description

Indicates the message text output when the alarm event occurs.

Specifiable value

A string that is 0 to 255 bytes long and consists of double-byte and/or single-byte characters.

Any spaces after equals signs (=) and before line returns are ignored.

If the equals sign is only followed by spaces, these spaces are treated as not being specified.

When the function for suppressing the execution of remote actions when an alarm is returuned to normal by user operation is enabled, do not set any of the following statements in the alarm message text of alarm definitions. If you do not observe this, no action is executed upon successful recovery from the alarm state.

  • "Alarm deactivated"

  • "Alarm cleared"

  • "Alarm updated/deleted"

Omissible

Yes

Table 3‒55: Check Value Exist label

Type

Description

Description

Indicates whether the alarm monitors the existence of a value.

Specifiable value

Y or N can be specified.

  • When Y is specified

    The alarm is defined as monitoring the existence of the value.

  • When this is omitted or N is specified

    The alarm is defined as a normal alarm.

Omissible

Yes

  • Advanced Setting subsection

    Specifies extended alarm information (such as the alarm type and monitoring time). This subsection can be omitted.

    The labels that can be specified for this subsection are as follows.

    Note that you can specify the Notify State label only when the value of the Alarm Definition File Version label is 0002.

Table 3‒56: Active Alarm label

Type

Description

Description

Indicates the alarm status.

Specifiable value

Y or N can be specified.

  • When this is omitted or Y is specified

    The alarm is enabled.

  • When N is specified

    The alarm is disabled.

Omissible

Yes

Table 3‒57: Regular Alarm label

Type

Description

Description

Indicates whether the alarm setting Always notify is enabled.

Specifiable value

Y or N can be specified.

  • When Y is specified

    Always notify is enabled.

  • When this is omitted or N is specified

    Always notify is disabled.

Omissible

Yes

Table 3‒58: Evaluate All Data label

Type

Description

Description

Indicates whether the alarm setting Evaluate all data is enabled.

Specifiable value

Y or N can be specified.

  • When Y is specified

    Evaluate all data is enabled.

  • When this is omitted or N is specified

    Evaluate all data is disabled.

Omissible

Yes

Table 3‒59: Notify State label

Type

Description

Description

Indicates whether to enable the notification of a change of status.

Specification format

Notify State=Alarm|Instance

Specifiable value

Alarm or Instance can be specified.

  • When Alarm is specified

    Notification of alarm status changes is carried out.

  • When Instance is specified

    Notification of state changes for each instance is carried out.

Omissible

Yes (When omitted, specification of Alarm is assumed.)

Remarks

When Instance is specified, a syntax error occurs if the value of the Regular Alarm label and Evaluate All Data label is Y.

Table 3‒60: Monitoring Regularly label

Type

Description

Description

Indicates whether the Always monitor alarm setting is enabled.

Specifiable value

Y or N can be specified.

  • When this is omitted or Y is specified

    Always monitor is enabled.

  • When N is specified

    Always monitor is disabled.

Omissible

Yes

Table 3‒61: Monitoring Time label

Type

Description

Description

Indicates the monitoring time when the Always monitor alarm setting is disabled.

Specifiable value

start-time-end-time

This specifies the local time in HH:MM format. start-time and end-time are joined with a hyphen (-).

  • HH: Specifies the start time hour, from 00 to 23.

  • MM: Specifies the start time minute, from 00 to 59.

Omissible

Yes (but not when the value of the Monitoring Regularly label is N)

Table 3‒62: Damping label

Type

Description

Description

Indicates whether the Report alarm when the following damping condition is reached alarm setting is enabled.

Specifiable value

Y or N can be specified.

  • When Y is specified

    Report alarm when the following damping condition is reached is enabled.

  • When this is omitted or N is specified

    Report alarm when the following damping condition is reached is disabled.

Omissible

Yes

Table 3‒63: Damping Count label

Type

Description

Description

Indicates the number of times the threshold was exceeded and the measurement interval, when the Report alarm when the following damping condition is reached alarm setting is enabled.

Specifiable value

number-of-times-threshold-exceeded/interval-value

Integers from 1 to 32767 can be specified for number-of-times-threshold-exceeded and interval-value, joined with a slash (/).

If interval-value is less than number-of-times-threshold-exceeded, interval-value is treated for processing as having the same value as number-of-times-threshold-exceeded. This cannot be omitted when the value of the Damping label is Y. If the value of the Damping label is N, or the label is omitted, this specification is ignored.

Omissible

Yes (but not when the value of the Damping label is Y)

  • Check Value Exist subsection

    If the Monitor whether the value exists alarm setting is enabled, this subsection specifies the record and values to be monitored. This subsection can be omitted, except when the Check Value Exist label is set to Y in the General subsection.

    The labels that can be specified for this subsection are as follows.

Table 3‒64: Record label

Type

Description

Description

If the Monitor whether the value exists alarm setting is enabled, this shows the records for the target to be monitored.

Specifiable value

This specifies the record ID of the records to monitor, in 1 to 7 single-byte characters.

You can specify only the record ID of a multi-instance record.

For details about record IDs, see the chapter in the PFM - Agent or PFM - RM manuals that describes records.

Omissible

No

Table 3‒65: Field label

Type

Description

Description

If the Monitor whether the value exists alarm setting is enabled, this shows the record fields for the target to be monitored.

Specifiable value

This specifies the PFM - Manager name for the fields to be monitored, in 1 to 50 single-byte characters.

Omissible

No

Table 3‒66: Value label

Type

Description

Description

If the Monitor whether the value exists alarm setting is enabled, this shows the value to monitor for existence.

Specifiable value

The value that can be specified differs depending on the field value. You can specify an integer, a fractional value, or a string that is 1 to 127 bytes long and consists of double-byte and/or single-byte characters.

Control characters and (, ), [, ], <, >, =, or " cannot be specified. To specify these characters, use the wildcard character to specify the values. To use the hash mark (#) in the value to monitor for existence, specify \#. To use the backslash (\) in the value to monitor for existence immediately before a specified wildcard character, use \\.

Omissible

No

  • Alarm Condition Expressions subsection

    This subsection specifies records and values to be monitored by alarms. This subsection can be omitted, except when the Check Value Exist label does not exist in the General subsection, or is set to N.

    The labels that can be specified for this subsection are as follows.

Table 3‒67: Condition label

Type

Description

Description

Indicates the conditional expressions for monitoring by using an alarm.

Specifiable value

Conditional expressions for monitoring by using an alarm are specified in the following format:

<monitored-field><condition><abnormal-value>,<warning-value>

  • <monitored-field>

    Specifies the PFM - Manager name of the record ID and field to be monitored, as a string from 1 to 50 single-byte characters joined by an underscore (_).

  • <condition>

    One of the following is specified.

    =: The field value is equal to the specified value

    <: The field value is less than the specified value

    <=: The field value is less than or equal to the specified value

    >: The field value is greater than the specified value

    >=: The field value is greater than or equal to the specified value

    <>: The field value is not equal to the specified value

  • <abnormal-value>,<warning-value>

    Specifies the threshold used as the standard for determining abnormal or warning alarms (values are separated by a comma (,)).

    Specify a period (.) as the decimal point.

    Specify an integer, a fractional value, or a string (consisting of double-byte and/or single-byte characters). The values that can be specified differ depending on the monitored field. Control characters and (, ), [, ], <, >, or = cannot be specified. When a string is specified, the string needs to be enclosed by double quotation marks ("). If the string contains tab symbols (\t), all such symbols will be replaced with spaces.

To set multiple conditions, join each condition with AND. As many as five conditional expressions can be specified together. If multiple conditional expressions are specified, they are evaluated in the order specified (starting with the expression that begins from the left). Note that if measurement values are displayed by using %CVS variables, field locations are determined in the order specified (starting with the expression that begins from the left). If an alarm definition that contains three or more conditional expressions is displayed in PFM - Web Console, these conditional expressions are listed within parentheses (()) in the priority order (the expression with the lowest priority comes first).

Example:

Definition imported by using the jpctool alarm import command: A AND B AND C

Definition displayed in PFM - Web Console: A AND ( B AND C )

When an alarm for which the conditions for the abnormal value and warning value are different (such as abnormal value < 50 and warning value <= 60) is exported, the warning value is given priority for export (or the abnormal value if the warning value does not exist). When an alarm with no abnormal value or warning value is exported, <abnormal-value> or <warning-value> are left blank.

When registered to PFM - Manager, conditional expressions are divided into abnormal conditions and warning conditions. An error will occur and registration will fail when the length of any conditional expression exceeds 749 bytes. The length of conditional expressions that can be registered with PFM - Manager can be calculated by the following formula, where n (1≤n≤5) represents the number of conditional expressions specified together using AND (1≤in). An error will occur if the value calculated by the following formula exceeds 749 bytes.

Length of conditional expression for abnormal values = [Figure]

Length of conditional expression for warning values = [Figure]

ai: The length of the ith <monitored-field>, in bytes

bi: The length of the ith <condition>, in bytes

ci: The length of the ith <abnormal-value>, in bytes. When a string is specified, the length does not include quotation marks.

di: The length of the ith <warning-value>, in bytes. When a string is specified, the length does not include quotation marks.

Omissible

No

  • Actions subsection

    This subsection specifies the actions executed and reports displayed when an alarm event occurs. This subsection can be omitted.

    The labels that can be specified for this subsection are as follows.

Table 3‒68: Report label

Type

Description

Description

Indicates the name of the displayed report when the alarm event occurs.

Specifiable value

An absolute path of the folder tree (from the Reports/ folder) that is 0 to 1,024 bytes long and consists of double-byte and/or single-byte characters.

If the name contains \ or / (except for the folder separator character), each should be entered as \\ and \/. If the label value or label itself is omitted, this specification is treated as unspecified.

Omissible

Yes

Table 3‒69: E-mail label

Type

Description

Description

Indicates the alarm event for the e-mail execution target of the action executed by the alarm.

Specifiable value

The following values can be specified.

  • For abnormal value execution: Abnormal

  • For warning value execution: Warning

  • For normal value execution: Normal

To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,).

The statuses are in random order, but an error will occur if the same status is specified more than once.

Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection.

Omissible

Yes

Table 3‒70: Command label

Type

Description

Description

Indicates the alarm event used as the command execution target for the action executed by alarm.

Specifiable value

The following values can be specified.

  • For abnormal value execution: Abnormal

  • For warning value execution: Warning

  • For normal value execution: Normal

To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,). The statuses are in random order, but an error will occur if the same status is specified more than once.

Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection.

Omissible

Yes

Table 3‒71: SNMP label

Type

Description

Description

Indicates the kind of statuses for which an alarm performs SNMP trap notification.

Specifiable value

The following values can be specified.

  • For abnormal value execution: Abnormal

  • For warning value execution: Warning

  • For normal value execution: Normal

To perform execution on multiple alarm events, specify a string indicating the statuses, with each status separated by a comma (,). The statuses are in random order, but an error will occur if the same status is specified more than once.

Warning cannot be specified when the Check Value Exist label is set to Y in the General subsection. Normal cannot be specified when the Regular Alarm label is set to Y in the Advanced Setting subsection.

Omissible

Yes

Table 3‒72: JP1 Event label

Type

Description

Description

Indicates whether JP1 event execution is set for action execution.

Specifiable value

Y or N can be specified.

  • When Y is specified

    A JP1 event is executed for the action.

  • When this is omitted or N is specified

    This is disabled.

If no value is specified for the Command label, this specification is ignored.

Omissible

Yes

  • Action Definition E-mail subsection

    This subsection specifies the settings for executed actions (e-mail) when an alarm event occurs. This subsection can be omitted, except when e-mail execution is specified in the Actions subsection.

    The labels and sub-subsections that can be specified for this subsection are as follows.

Table 3‒73: E-mail Address label

Type

Description

Description

Indicates the e-mail recipient.

Specifiable value

The value can be specified in 1 to 127 single-byte characters. Multiple recipients can be specified by separating each with a comma (,). In this case, the total length must be within 127 bytes.

Omissible

No

Table 3‒74: Action Handler label

Type

Description

Description

Indicates the service ID of the action handler for which e-mail is sent.

Specifiable value

The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL.

Omissible

No

Table 3‒75: Message Text sub-subsection

Type

Description

Description

Indicates the message contents sent by e-mail.

Specifiable value

A string that is 0 to 1,000 bytes long and consists of double-byte and/or single-byte characters.

In this sub-subsection, contents until the first line of the next section or subsection, or end of the file (EOF), can be set as the defined value. Note that any comments in the sub-subsection are excluded. Also, valid line return characters in the final line of the sub-subsection are excluded.

Omissible

Yes

  • Action Definition Command subsection

    This subsection specifies settings for executed actions (command) when alarm events occur. This subsection can be omitted, except when command execution is specified in the Actions subsection, and the value of the JP1 Event label is set to N (this is ignored when the JP1 Event label is set to Y).

    The labels and sub-subsections that can be specified for this subsection are as follows.

Table 3‒76: Command Name label

Type

Description

Description

Indicates the name of the command (script) executed for the action.

Specifiable value

The value can be specified in 1 to 511 single-byte characters.

When specifying this label, specify an absolute path or relative path from the current service directory when using a command (script) other than those in the following directories:

  • Action Handler service installation directory

  • Path set in the PATH environment variable

If the command path or command name to be specified includes at least one single-byte space character, enclose the command path or command name in double quotation marks (" ").

Omissible

No

Table 3‒77: Action Handler label

Type

Description

Description

Indicates the service ID of the action handler for which the command is executed.

Specifiable value

The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL.

Omissible

No

Note

Depending on the alarm action setting specified in the PFM - Web Console, the load might concentrate on the PFM - Manager host. To prevent this, open the New Alarm > Action Definitions page or the Edit > Action Definitions page, and then, in the Command field, select LOCAL for the command execution action handler. If you want actions to be triggered by alarms in a large-scale system, make sure that you select LOCAL to prevent the PFM - Manager host from being heavily loaded.

Table 3‒78: Message Text sub-subsection

Type

Description

Description

Indicates parameters to pass to executed commands.

Specifiable value

A string that is 0 to 2,047 bytes long and consists of double-byte and/or single-byte characters.

In this sub-subsection, contents until the first line of the next section or subsection, or end of the file (EOF), can be set as the defined value. Note that any comments in the sub-subsection are excluded. Also, valid line return characters in the final line of the sub-subsection are excluded.

Omissible

Yes

  • Action Definition JP1 subsection

    This subsection specifies settings for actions (JP1 events) executed when an alarm event occurs. This subsection can be omitted, except when command execution is specified in the Actions subsection, and the JP1 Event label is set to Y.

    The labels that can be specified for this subsection are as follows.

Table 3‒79: Event ID label

Type

Description

Description

Indicates the event ID sent to the JP1 event.

Specifiable value

The event ID is specified as a hexadecimal number. Values from 0 to 1fff and 7fff8000 to 7fffffff can be specified.

Omissible

No

Table 3‒80: Action Handler label

Type

Description

Description

Indicates the action handler to be executed for the JP1 event.

Specifiable value

The value can be specified in 1 to 258 single-byte characters. Even when the product name display functionality is enabled, the product name cannot be specified. To specify a local action, specify LOCAL.

Omissible

No

Table 3‒81: Message label

Type

Description

Description

Indicates the message sent to the JP1 event.

Specifiable value

A string that is 0 to 1,023 bytes long and consists of double-byte and/or single-byte characters.

To issue JP1 events with the Action Handler service in version 09-00 or earlier, specify a string that is 0 to 128 bytes long and consists of double-byte and/or single-byte characters.

Omissible

Yes

Table 3‒82: Switch Alarm Level label

Type

Description

Description

Indicates whether the alarm level is converted to a JP1 event priority.

Specifiable value

Y or N can be specified.

  • When this is omitted or Y is specified

    The action alarm level is converted to an event priority in the JP1 event.

  • When N is specified

    This is disabled.

Omissible

Yes

Table 3‒83: Exec Logical Host label

Type

Description

Description

Indicates the name of the event server registered for the JP1 event. Specified when the event server is operating on a logical host.

Specifiable value

The value can be specified in 0 to 255 single-byte characters. If no value is specified, this is treated as being omitted.

Omissible

Yes

The following shows an example of an alarm definition file.

Example of an alarm definition file

Alarm Definition File Version=0002
Alarm Definition File Code=US_ASCII
 
[Alarm Data]
[[General]]
Product=T3.0
Alarm Table Name=Example
Alarm Name="CPU Usage"
Message Text="CPU is at %CVS% utilization"
Check Value Exist=N
 
[[Advanced Setting]]
Active Alarm=Y
Regular Alarm=N
Evaluate All Data=N
Notify State=Alarm
Monitoring Regularly=Y
#Monitoring Time=
Damping=Y
Damping Count=2/3
 
#[[Check Value Exist]]
#Record=
#Field=
#Value=
 
[[Alarm Condition Expressions]]
Condition=PI_PCT_TOTAL_PROCESSOR_TIME>90.000000,80.000000
 
[[Actions]]
Report="Reports/Windows/Operating System/Troubleshooting/Real-Time/CPU Usage - Top 10 Processes"
E-mail=Abnormal,Warning
Command=Abnormal
SNMP=Abnormal,Warning,Normal
JP1 Event=N
 
[[Action Definition E-mail]]
E-mail Address=administrator@example.com
Action Handler=PH1host01
[[[Message Text]]]
Date: %SCT
Host: %HNS
 
Product: %PTS
Agent: %ANS
 
Alarm: %AIS (%ATS)
State: %SCS
 
Message: %MTS
[[Action Definition Command]]
Command Name=userprogram.exe
Action Handler=LOCAL
[[[Message Text]]]
%CVS
#[[Action Definition JP1 Event]]
#Event ID=
#Action Handler=
#Message=%MTS
#Switch Alarm Level=Y
#Exec Logical Host=

Notes

Return values

0

The command terminated normally.

1

An argument specification is invalid.

2

The user does not have execution permission for the command.

3

At least one of the Name Server, Master Manager, and View Server services is not running.

4

The startup stop command or another setup command was executed on the same machine.

5

The command was executed on a host that is not the PFM - Manager host. Or else, an attempt was made to execute the command from the secondary PFM - Manager host when multiple monitoring is performed.

6

There is an error in the contents of the alarm definition file.

11

The user canceled the processing.

13

The notification of state changes for each instance cannot be specified because the alarm table is bound to an agent that does not support the notification of state changes for each instance.

100

The Performance Management environment is invalid.

200

A memory shortage occurred.

210

A disk space shortage occurred.

211

Alarm definition file cannot be accessed, or alarm definition or updating failed because the alarm was being updated.

222

A communication error occurred.

223

Communication processing resulted in a timeout.

255

An unexpected error occurred.

Usage example

This example imports the alarmtest1.cfg alarm definition file stored in the /tmp directory:

jpctool alarm import -f /tmp/alarmtest1.cfg