ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 132 of 381
issue a MONITOR command that contains an object filename. A user must manually
delete the aggregate-only domain for individual records on each object to be written to
the historical database. For example if you enter MONITOR PROCESS
$DATA.OBJECT.FILE, then ASAP issues a MONITOR PROCESS
$DATA.OBJECT.FILE\## command to add an aggregate-only domain. For more
information on aggregate and aggregate-only domains, see the sections on
aggregation later in this section.
Object filename domains that are resolved at each interval are stored in a memory
pool in the Process SGP. The pool is allocated from extended memory and is
controlled by KMSF. Excessive numbers of objects can deplete the pool space. The
MONITOR PROCESS, LIST, DETAIL command can be used to view pool usage and
the MBYTES parameter to the ASAP Process SGP process is used to control the
amount of space within the pool. For more information, see the MONITOR Command
and PROCESS option in the SET Command.
To set an objective on a domain resolved from an object filename you must include the
object filename specifier in the name. For example, to set an objective on the Full
attribute for process $ABC that was resolved from the $DATA.OBJECT.FILE object
filename specifier, enter RANK PROCESS $DATA.OBJECT.FILE\$ABC, FULL <
90. You can also set a global objective at the object filename level; for example, RANK
PROCESS $DATA.OBJECT.FILE, BUSY < 95.
Note
Resolving the processes running from an object filename can result in excessive low-level
messaging in the NonStop OS. This method should be used judiciously in extremely high-
performance application environments.
Monitoring Files and Processes Using OSS
Pathnames
OSS pathnames can be specified as domain names or separately using the PATH
option to the MONITOR command when monitoring OSS files and processes.
Because OSS pathnames can be longer and can contain more levels than ASAP
domain names, ASAP truncates any OSS pathname specified as a domain name
when the entire domain name exceeds 64 bytes or contains more than 5 levels. ASAP
truncates the leftmost portion of the pathname and includes a partial filename but not
the partial directory levels. Only entire directory levels are included, and only when the
level does not exceed the maximum level requirement.
ASAP transforms the pathname portion of a domain name into proper ASAP domain
name form, using the backslash as the level separator instead of a slash. When you
enter MONITOR PROCESS /bin/sh and ASAP finds a process running from the /bin/sh
object file, it creates a new record for that process by adding the process identifier as a
new level. An actual domain that would be displayed in an ASAP record would be