ASAP 2.8 Server Manual

Introduction to Availability Statistics and
Performance (ASAP)
HP NonStop ASAP Server Manual—522303-007
1-10
Command and Control
ASAP performance information is stored in a structured real-time availability database
that user programs can easily access. The structure of this normalized database is
documented in each release of ASAP. To generate DDL data structures that you can
use in your program for accessing the ASAP database, refer to the released file
ASPDDLDB.
Command and Control
The ASAP Conversational Interface provides commands and options that let you work
interactively with the collection system:
•
STATUS, STARTUP, and SHUTDOWN commands control the ASAP Monitor and
Collector processes. When any entity is configured for gathering entity availability
information, the ASAP Monitor process also starts the selected entities.
•
The SET command controls the ASAP environment and is also used for setting
individual SGP options. See SET Command on page 6-87.
•
Display formats for application entities are defined in EDL.
•
All entity commands display current availability reports or reports from different
times when the command is followed by TIME hh:mm.
Database
The ASAP database contains current and historic normalized system, Application,
COMM SGP, CPU, Disk, Expand line-handler, File, Node end-to-end, Process,
ProcessBusy, RDF, Spooler, Tape, and TMF availability information. The database
records for all entities also contain operational state information.
Database features include:
•
Quick retrieval of statistical information.
•
Automatic long-term availability and performance history data.
•
No remote disk space requirement for availability information. Remote object file
space is required.
•
Database maintenance functions:
•
Fast Cleanup for immediate deletion of all records.
•
Daily deletion of all records at a user-specified time.
•
Daily retention of recent records. You define the number of records to retain.
•
The Rollover option renames entity database files daily so you can archive
them for historic analysis at a later date.
Once started, ASAP needs no operator intervention. Even when CPUs become
unavailable, the ASAP database is automatically maintained.