ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 85 of 381
Example A
Example A defines a set of ASAP processes that report statistics for all nodes in the
network to the Chicago node:
SET COLLECT \CHICAGO !define collection node
SET DB $DATA.ASAPDB.DB !define database location
SET RATE 15 !define sample interval
SET DISK ON !Enable disk reporting
SET ID $CHI !ID for first process set
START \CHICAGO COLLECT !Start collector on \Chicago
START \* !Start monitors & SGPs on all nodes in the network
Example B
Example B defines a second set of processes that report statistics for a selected
regional group of nodes to the LA node:
SET COLLECT \LA !define collection node
SET DB $DATA2.ASAPDB.DB !define database location on \LA
SET RATE 5 !define sample interval
SET DISK ON !Enable disk reporting
SET ID $LA !ID for second process set
START \LA COLLECT !Start collector on \LA
START \LA !Start \LA monitor and SGPs
START \SANFRAN !Start \SanFran monitor and SGPs
START \SEATTLE !Start \Seattle Monitor and SGPs
START \DALLAS !Start \Dallas monitor and SGPs
Viewing the ASAP Event Log
By default, the Monitor and Collect or processes on each node automatically create
and maintain a small log file named $SYSTEM.SYSTEM.ASAPLOG. In addition, log
messages are written to the operator or Viewpoint console, $0. You can enter the
ASAP LOG command to display recent ASAPLOG messages.
ASAP HELP ERROR displays a description of all log error and information message
formats. In general, log messages are informational. ASAP should recover from all
situations except a total node failure.
This is the output from the ASAP event log file:
Date Time Msg# PID Message text Parms
----- ------ ---- ---- ------------------ ---------
08/02/28 0613:19 1881 ZOOH INFO ASAPXSGP V03 (15APR2008) started 1
08/02/28 0613:20 1023 ZOOJ INFO SGP DSK V03 (15APR2008) started 1
08/02/28 0613:22 1881 ZOOH1INFO ASAPXMON V03 (15APR2008) started 1
08/02/28 0613:22 1881 ZOOH0INFO ASAPXMON V03 (15APR2008) started 0