3.6.1 HP PolyServe Matrix Server Administration Guide (T5392-96018, August 2008)

Chapter 13: Configure Event Notifiers and View Events 170
Script Requirements
For the script to work properly, the following requirements must be met:
• The script or program must be accessible from each node in the
cluster. It is recommended that an identical copy of the script or
program be placed on local storage on each node to ensure that it will
always be available.
• The script must be able to be executed on each node. For example, if
perl or Powershell is used, the appropriate interpreter must be
installed on each node and the appropriate extension must be
associated with the interpreter on each node.
• The script or program must either use full path names to any external
commands or set a PATH variable appropriate to each language. (A
system PATH variable is not passed to the script.)
Script Variables
Variables are accessed in a manner consistent with the language. For
example, the VA R variable is accessed in Batch as %VAR%; Powershell
uses $env:VAR; C uses getenv("VAR"); perl uses $ENV{VAR}; and so on.
The following variables can be set for an event. (All of the variables are
not required for each event).
MxS-event-cluster-description MxS-event-severity-name
MxS-event-cluster-id MxS-event-category
MxS-event-epoch MxS-event-source
MxS-event-serial MxS-event-event-time
MxS-event-event-id MxS-event-location
MxS-event-catalog-version MxS-event-process-id
MxS-event-severity MxS-event-message
MxS-event-user