ASAP 3.0 Server Manual

HP NonStop ASAP Server Manual Page 62 of 342
ASAPFIL Object File
The ASAP Monitor starts the File SGP on its node if File is enabled. The ASAP
Statistics Gathering (ASAPFIL) Process collects availability information for user-
selected files or subvolumes. The utilization counters gathered include percent file full,
number of files in the subvolume, and number of partitions.
ASAPMON Object File
The ASAP node Monitor (ASAPMON) process manages all node-level processing for
the network node on which it is running, and creates the Statistics Gathering
processes (SGPs) in each CPU of the node where it is located. These SGPs collect
CPU availability information and PROCESSBUSY availability information for the CPU
in which it resides. System availability is the average availability for all the monitored
CPUs on the node. The ASAP Monitor monitors CPU up and down messages, stop or
abend messages, and creates the SGPs according to the changing status of the
CPUs. The ASAP Monitor also starts the node entity SGPs, APP, Disk, File, Node,
Process, RDF, Spooler, Tape and TMF.
The ASAPMON processes use special NonStop OS procedures to collect CPU,
Processbusy, and System Availability information.
This object file is required on all monitored nodes.
When the ASAP Conversational Interface (CI) starts a remote ASAP Monitor process,
the Monitor starts various monitoring functions specified in the ASAPCONF file or from
interactive user commands. The ASAP Monitor is responsible for starting and
maintaining the proper monitoring software in its node. If any Monitor or Statistics
Gathering process (SGP) goes down for any reason, the ASAP Monitor in that node
coordinates an automatic restart of processes as needed. For example, if a CPU fails
and comes back online, the CPU SGP for that CPU is restarted. Or, if a remote ASAP
Monitor process fails, its backup process takes over since the ASAP Monitor process
is continuous.
The remote ASAP Monitor starts the CPU SGP in each CPU of the monitored node.
CPU SGPs are responsible for gathering CPU-level statistics, including CPU
performance metrics, Operational state, and information about the busiest processes
in their CPU. The CPU SGPs report CPU-level information to the ASAP Monitor
process. The Monitor bundles this information into a single message and forwards it to
the ASAP Collect process on the main Collection node. The Collect process parses
this information and stores it in the normalized ASAP database. The data can be
displayed with the ASAP CPU and PROCESSBUSY commands, or with various block-
mode or workstation programs.
ASAPNCP Object File
The ASAP Monitor starts the Node SGP on its node if the Node SGP is enabled. The
ASAP Statistics Gathering (ASAPNCP) Process collects statistics for the Expand end-