ASAP 3.0 Server Manual

HP NonStop ASAP Server Manual Page 60 of 342
Process (SGP)
monitored tape device on the node.
ASAPTCP
TCP Statistics Gathering
Process (SGP)
Gathers availability and statistics
information for nine TCP/IP entities and
three Telserv entities.
ASAPTMF
TMF Statistics Gathering
Process (SGP)
Gathers availability information for the
TMF subsystem on the node.
ASAPXSGP
ASAP Statistics Gathering
Process (SGP)
Gathers service-level metrics about
customer applications. It is an optional
product, part of the ASAP Extension
product (ASAPX).
These descriptions of the ASAP object files explain which ASAP components are
required on various nodes of the network:
ASAP Object File
The object file ASAP is the ASAP Conversational Interface (CI), which starts and
manages the Monitor and Collector processes, and displays the collected ASAP
availability information. The ASAP CI provides command and control of the ASAP
environment and enables interactive reporting of availability information. STATUS,
STARTUP, and SHUTDOWN commands control Monitor and Collect processes. Use
the SET command to set up options for the Monitor, Collector, and the Statistic
Gathering processes. APP, CPU, DISK, FILE, LH, NODE, PROCESS,
PROCSSBUSY, RDF, SPOOLER, SYSTEM, TAPE and TMF commands provide ad
hoc statistics reports. For the syntax and detailed descriptions of these commands,
see Section 6: ASAP Conversational Interface Commands.
This object file resides only on the collection node.
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.
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