ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 65 of 381
ASAPCONF File
The ASAPCONF file contains configuration information for the ASAP and ASAP
Extension subsystems. Before trying to start the ASAP and ASAPX subsystems, make
sure that they are properly installed.
ASAPDSK Object File
The ASAP Monitor starts the Disk SGP on its node if Disk is enabled. The ASAP
Statistics Gathering (ASAPDSK) Process collects availability information for the ASAP
for all nonphantom disk devices. ASAPDSK uses the Measure Programmatic Interface
to obtain raw disk counters from the disk process. For a complete list of Disk
availability counters, see the DISK Command.
ASAPEXP Object File
The ASAP Monitor starts the Expand SGP on its node if Expand is enabled. The ASAP
Statistics Gathering (ASAPEXP) Process collects availability information for the
Expand line handlers. The utilization counters gathered include page faults, BCC,
Naks sent and received, and packets sent and received. For a complete list of the
Expand availability counters, see the LH Command. The Expand SGP communicates
directly with the Expand Manager process to get Expand availability information.
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. For a complete list of file
availability counters, see the FILE Command.
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.