ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 82 of 381
The STATUS command returns the node name, the process ID and version, and all of
the SGPs that are running on the node. In this example, the SGPs are $ZOO1 and
$ZOOJ. The options in parentheses for the Monitor process are also displayed.
You can also use the ASAP LOG command to get more node status information. For
example:
LOG \CHICAGO
Starting ASAP With the Default Configuration
When the Monitor starts, it starts the SGPs that were set to ON. The SGPs get the list
of domains they should monitor from the Objectives Database. Each SGP configures
some domains by default when no entity records are found in the Objectives Database.
For more information, see MONITOR Usage Considerations.
Changing the ASAP Configuration
Dynamically
You can dynamically modify the ASAP configuration once the SGPs start.
For example, to add a new File domain, set one global File objective, one specific File
objective, specify EMS event generation for both objectives, add a new Process
domain, configure a specific objective with EMS event generation specification, then
commit the changes:
+MONITOR FILE $SYSTEM.SYSTEM.USERID, ADD
+RANK FILE, FULL < 90 CRITICAL
+RANK FILE $SYSTEM.SYSTEM.USERID, owner="255,255" CRITICAL REPEAT
+MONITOR PROCESS $ZOOS, ADD
+RANK PROCESS $ZOOS, PRI >= 160 CRITICAL REPEAT
+COMMIT
After the COMMIT command executes, the changes appear at the next sampling
interval for each entity. You can also dynamically DELETE domains or objectives,
then use the COMMIT command to activate those changes. For command
descriptions, see Section 6: ASAP Conversational Interface Commands.
Viewing Statistics
Although the regular user interface to view ASAP statistics is the ASAP Client, you can
use the ASAP CI can display those statistics by using the entity name as the command
name. For example, to view statistics for the DISK, PROCESSBUSY and SPOOLER
entities: