ASAP 3.0 QuickStart Guide

HP NonStop ASAP QuickStart Guide Page 26 of 35
become active. Once you have defined your set of objects to be monitored, you can activate
monitoring via a single COMMIT command.
+ COMMIT
At this point ASAP will remove the non-existing CPUs (4-15), and will only report data on the
CPUs that you are specifically monitoring, CPUs 0-3.
When you enter a MONITOR command against any ASAP entity (subsystem), then you
assume responsibility for the configuration for that entity. For example, you might have 30
disks on your system which ASAP will auto-configure and automatically monitor at startup
time. But if you enter a MONITOR DISK $DATA command, then ASAP will assume that you
want to control the set of monitored disk objects and will only monitor the $DATA disk from
that point forward (unless you specify additional disks to be monitored via subsequent
MONITOR commands).
ASAP automatically configures all objects it can find to monitor for all entities (subsystems),
except the File and Process entities. ASAP does not automatically monitor all Files and
Processes since there could be literally thousands, tens of thousands, or hundreds of
thousands of these objects. For this reason ASAP, by default, only monitors its main
process (by default $ZOOM) and the object file for its main process (by default
$SYSTEM.SYSTEM.ASAPMON). If you want to monitor additional files or processes, then
you need to specify those objects using monitor commands.
ASAP provides many ways to monitor files and processes: by their names, by using wildcard
names, or by grouping them into logical groups and aggregating data over the set of objects
in the group. Please see the ASAP Server manual for more information on File and Process
monitoring.
The key point to rememberfrom this section is that you use the MONITOR command to tell
ASAP which objects to monitor on your NonStop server.