The ACTION command allows you to specify an action AMS should perform when it matches a pattern to a message. You can specify any number of actions per pattern. Most actions are executed in the order in which you specify them. Exceptions are ACTIVATE and DEACTIVATE, which are always executed last, and HOLD actions, which are executed after all RELEASE actions.
Format
[SP‑AMS]
ACTION action-type "action-text" [WAIT nn [<SECONDS>| MINUTES] ]
[CP‑AMS]
ACTION operation-mode ...action-type "action-text" [WAIT nn [<SECONDS>| MINUTES] ]
where:
operation-mode [CP-AMS]
is the mode to which the action applies. In CP-AMS, you must specify at least one mode. You can specify any combination of the following:
ATTENDED (executed only when the OM keyin option AAMS=ON)
CASUAL
UNATTENDED
ALL
is the type of action AMS should perform. You can specify the following automation actions:
Subsections 4.4 through 4.19 describe the various action types.
is required for all actions except DEACTIVATE, HOLD, and SUPRESS. Action text is stored in the database in the case in which you specify it. action-text is described further in 4.3, and in the description of each action that requires action text.
WAIT
use to delay the execution of an action for a specified number of seconds or minutes.
nn is an integer between 1 and 32767 that indicates the number of seconds or minutes to wait before performing the action. You must specify the integer as a constant; you cannot refer to a variable for the integer value.
SECONDS is the default if you specify neither SECONDS nor MINUTES.
Generated and then saved until the specified number of seconds or minutes have elapsed.
Executed once the specified time has elapsed. The delay is no less than the amount of time specified but could be slightly longer.
Executed even if no database is still active at the time that the specified number of seconds or minutes has elapsed.
Not executed if the autoaction process terminates for any reason, such as a system crash or an error in AMS.
When WAIT is used with ACTIVATE or DEACTIVATE, the specified database is activated or deactivated after the elapsed amount of time. If an operator activates another database between the time that the ACTIVATE or DEACTIVATE action is executed, the database that is specified in the delayed action is still activated at the specified time.
[SP‑AMS]
Turning the system monitor off and then back on has no effect on queued timed actions. If the timer for a delayed COMMAND or PASSWORD action expires and Operations Sentinel Console is not managing the target system, the command cannot be sent to the system and SP‑AMS issues a warning. If monitoring is turned back on before the timer expires, the command is sent to the system.