ASAP 2.8 Server Manual

File and Process Monitoring
HP NonStop ASAP Server Manual—522303-007
5-3
Monitoring Files and Processes Using OSS
Pathnames
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 on
page 6-53 and PROCESS option in the SET Command on page 6-87.
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.
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
Bin\Sh\$Name for a process named $Name or might be Bin\Sh\$.2.59.6181274 for the
unnamed process running in CPU 2, PIN 59.
The OSS pathname can be the complete domain name, as shown in the /bin/sh
example, or it can be preceded by a logical name as described in the next section. For
example, MONITOR PROCESS OSS\SHELL/bin/sh creates an ASAP domain name of
OSS\SHELL\BIN\SH. The name OSS\SHELL/bin/sh is equivalent to
OSS\SHELL\/bin/sh.
If OSS pathnames cannot work as a part of an ASAP domain name, or you do not like
the way ASAP converts the pathname into a domain name, you can create your own,
unique domain name and use the MONITOR command PATH option to specify the
OSS pathname.
All OSS pathnames must begin with a slash.
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.