ASAP 3.2 Server Manual
HP NonStop ASAP Server Manual Page 99 of 381
To change the event generated for all down processes to a repeating event:
RANK PROCESS, STATUS CRITICAL REPEAT
To change the event generated for failures of $Abc to an informative event:
RANK PROCESS $ABC, STATUS INFO
To turn off event generation for status changes to process $Def:
RANK PROCESS $DEF, STATUS NOEMS
By default, ASAP user-defined entities do not generate EMS events for Status
changes. Because a single process can register hundreds of user domains with ASAP,
failure of that process could generate hundreds of EMS messages. User-defined
entities are created to describe your applications that use the ASAP Extension to
register with ASAP. To turn on events for Status changes of user-defined entities:
To generate a nonrepeating critical event when the Status changes to a bad state
for any ATM domain:
RANK ATM, STATUS CRITICAL
To generate a critical event and repeat it at each interval whenever $Atm37 fails:
RANK ATM\CHICAGO\WEST\$ATM37, STATUS CRITICAL REPEAT
The ASAP Extension provides an API that applications can use to set the Status and
OpState for domains they register. Using the ASAPX API, an application gains direct
control over when ASAP generates an event on behalf of that application.
Event Considerations Summary
To turn on DOTs event generation, use the SET ObjectivesEvent ON and SET
ObjectivesEventUp ON commands in your ASAPCONF file.
To define when to generate events, set ObjectivesEventState,
ObjectivesEventMax, and other parameters.
To modify ASAP’s automatic generation of Status change events for system
objects, use GOAL, STATUS or RANK, STATUS.
To define the additional attributes for which you want events generated, issue
GOAL or RANK commands. For example, to generate a critical event if any CPU
exceeds 89% busy, enter RANK CPU, BUSY < 90 CRITICAL.