ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 64 of 381
ASAPCMM Object File
The Monitor starts the COMM SGP on its node if Comm is enabled. The ASAP
Statistics Gathering (ASAPCMM) Process collects availability information for all
monitored SWAN communication line types. ASAPCMM uses the Measure
programmatic interface to obtain raw communication line counters from the
communication processes. For a complete list of COMM availability counters, see the
COMM Command.
ASAPCOL Object File
The ASAP database includes current and historical information about system
performance and operational status of system objects. It is automatically created when
the ASAP Collect process is first started. The Collect process receives statistics and
status messages from ASAP monitors throughout the network, parses the messages,
and stores the information in the normalized ASAP database.
The Collect process automatically maintains the database. The Collect process
includes database maintenance options to specify how much history to retain. You can
configure database history to only retain data since the last cleanup time; for example,
every night at midnight. Or you can configure it to retain ASAP history for a longer
period of time, or indefinitely. For more information about database maintenance
options, see the SET RETAIN option under the SET Command.
The ASAP Collect process is continuous. If a CPU fails, the backup Collect process
automatically takes over so database access is always available. The ASAP database
is a real-time normalized database and can be queried online. The ASAP product
subvolume includes Enform queries that allow batch-type queries of network
performance and operational status.
The statistics Collect server (ASAPCOL) process runs continually and manages the
ASAP database. It:
 Creates and maintains ASAP structured files.
 Maintains statistics sent to the Collect process from various Monitor processes.
 Manages ongoing space management of active database files.
If you manually execute the ASAPCOL object file from a TACL prompt with a process
name of $APPDB, $CPUDB, $DSKDB, $NETDB, $SYSDB, $PCBDB, $EXPDB,
$FILDB, $PRODB, $RDFDB, $SPLDB, $TAPDB, or $TMFDB, it acts as an Enform
server rather than a Collect process. For information on how to use ASAPCOL as an
Enform server, see the ENFALL file in the ASAP distribution subvolume.