ASAP 3.0 QuickStart Guide

HP NonStop ASAP QuickStart Guide Page 34 of 35
Section 6: Automated Actions
The GOAL command can also be used to define automated actions that ASAP will execute
to fix a problem that might occur. Automated actions are an advanced topic and do not
really belong in this QuickState Guide but are included here to show you that they can be
defined. Please read about this capability in the ASAP Server Manual for more information.
When a problem is detected by a goal not being met and an action is defined for that goal,
ASAP sends information about the problem to its Action Server. The information is sent in a
group of tokens whose values are set based on the object where the problem occurred.
Here are the action tokens:
<#ENTITY>
The entity name
<#OBJECT>
The NSK or OSS object name
<#DOMAIN>
The domain name
<#D1>
Leftmost part of a multi-level domain name
<#D2>
2nd part of a multi-level domain name
<#D3>
3rd part of a multi-level domain name
<#D4>
4th part of a multi-level domain name
<#D5>
5th part of a multi-level domain name
<#ATTR>
The attribute name
<#OP>
The objective operator
<#VALUE>
The current value of the attribute
<#STATE>
The current state of the attribute
<#LASTSTATE>
The last state of the attribute
<#GOAL>
The objective value
The Action Server will retrieve the defined action from the ASAP goals/actions database and
will execute the action using the values for these tokens.
Here are some examples of automated actions:
1. This action reloads a failed CPU.
GOAL CPU, STATUS ACTION “TACL RELOAD <#OBJECT>, PRIME”
2. This action suspends a process that is too busy.
GOAL PROCESS, BUSY < 99 ACTION “TACL SUSPEND <#OBJECT>”
3. This action re-secures a file that isn’t secured correctly using a stored action rule
named SECURE.
GOAL FILE, RWEP = OOOO ACTION SECURE