ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 246 of 381
Using the << or <<< operator is the same as using the < operator if only one goal
is defined.
 To define a de-escalating goal on the TMF TRANSRATE attribute:
RANK TMF, TRANSRATE >30, TRANSRATE >> 20, TRANSRATE >>> 10
 To define an escalating goal on CPU BUSY that generates an information EMS
event and then a critical EMS event as the problem worsens:
RANK CPU, BUSY < 50, BUSY << 70 INFO, BUSY <<< 90 CRITICAL
The ―UP‖ event, if enabled, will be written when the CPU leaves the alert state by
falling back below 50% busy.
 To define an escalating goal on CPU BUSY that generates specific event numbers
and where the most critical event repeats while that level of problem exists:
RANK CPU, BUSY < 50 INFO 8881-8880
RANK CPU, BUSY << 70 CRITICAL 8882
RANK CPU, BUSY <<< 90 CRITICAL REPEAT 8883
If the CPU is 70% busy when it alerts then event 8882 will be written.
 To define an escalating goal on the SPOOLER FULLPCT attribute that takes a
different action depending on how full the SPOOLER is:
RANK SPOOLER, FULLPCT < 50 ACTION “TACL CLEANSPL <#OBJECT>”
RANK SPOOLER, FULLPCT << 70 ACTION “TACL DELETEJOB <#OBJECT>”
RANK SPOOLER, FULLPCT <<< 90 ACTION “TACL FORCESPL <#OBJECT>”
 To define a simplex goal for all CPUs and override that goal with an escalating
goal for CPU 0:
RANK CPU, BUSY < 60
RANK CPU 0, BUSY < 70, BUSY << 80, BUSY <<< 90
 To define a Boolean goal named BUSYGOAL for all CPUs that checks the BUSY
and QUEUE attributes and where failure of either will result in the goal failing:
RANK CPU, BUSYGOAL = (BUSY < 80 AND QUEUE < 3)
 To define a Boolean goal named BUSYGOAL for all CPUs that checks the BUSY
and QUEUE attributes and where failure of both are required for the goal to fail: