ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 15 of 381
 A process for gathering communication line statistics lets you collect availability
information for SWAN communication lines. For additional information, see the
SET COMM, and COMM commands.
 Specify which CPU the SGPs will execute. See the SET entity command.
 A Timeout option for the Status Monitor command lets you specify the elapsed
time for an ASAP SGP to reply. The Status command displays entity error
information in the unlikely event an SGP is in an error state or an SGP cannot
start. For additional information, see the STATUS Command.
 The ASAP monitor has been enhanced to restart SGPs at a 15-minute interval
when an SGP is accidentally stopped or is in an error state.
 ACTION, a parameter to the RANK Command, lets you define a specific recovery
action to take when the objective is not met.
 A new command, the ACTION Command, lets you define and list stored actions
and retrieve the stored action for a specific entity-domain-attribute-operator
combination.
 Process records contain two attributes in Process records. Count is the number of
domains. ACount is the number of attributes that are alerting when viewed at the
detail level, and is the number of domains that are alerting when viewed at the
aggregate level.
 You can:
 Monitor processes by their Guardian object filename or OSS pathname.
 Use wildcard process names to specify the processes to monitor.
 Logically group files and subvolumes into hierarchical groups.
 Aggregate data across any level of logical groupings of files.
 Write only aggregate file records to the historical database.
 Use wild-card file names to specify files to be monitored.
 Monitor OSS files by specifying the OSS pathname.
 Specify custom event numbers for specific objectives using the RANK
command. Custom event numbers in the range 6000 through 9999 are
available for this purpose.
 The OSS Permissions attribute has been added to file records.