ASAP 2.8 Server Manual

File and Process Monitoring

HP NonStop ASAP Server Manual—522303-007

5-4

Logical Grouping

ASAP lets you group files into hierarchical groups of files and processes into

hierarchical groups of processes. This feature is implemented in the MONITOR

command, allowing you to specify a logical group name or names that the file or

process belongs to. For example, these monitor commands define processes $A10

through $A14 as members of the Sales application:

Monitor Process Sales\Order\Entry\$A10

Monitor Process Sales\Order\Entry\$A11

Monitor Process Sales\Order\Fullfillment\$A12

Monitor Process Sales\Mfg\Build\Westcoast\$A13

Monitor Process Sales\Shipments\International\$A14

The rules for the logical domain names are:

1. The entire name must be between 2 through 64 bytes in length.

2. The name can contain up to five levels separated by a backslash.

3. The last level of the name must be an object selector: a filename or process name,

a wildcard file or process name, or a process object filename.

4. The name can be constructed with any printable ASCII character except a space,

colon, semicolon, quotation mark, or asterisk.

5. A physical file or process can belong to multiple groups.

Domain Aggregation

ASAP lets you aggregate File and Process domains at any level of the hierarchical

group name. ASAP can automatically construct aggregate domains for all objects at all

levels using a global parameter setting, or you can define only the necessary

aggregate domains for individual groups (recommended). Aggregate domain names

are constructed using the # character as the level name. For example, the aggregate

domain Sales\# represents the combination of all domains in the Sales group.

Similarly, Sales\Orders\# represents all members of the Sales\Order group.

There are two ways to turn on aggregation for files and processes being monitored as

a part of a hierarchical group.

Note. Resolving the processes running from an OSS pathname can result in excessive low-level

messaging in the NonStop OS. This method should be used judiciously in extremely high-performance

application environments.

Note. In this case, each file or process instance is monitored separately by ASAP and could

produce slightly different results depending on timing and other factors.