ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 211 of 381
Provider
is the name of a CIP Provider process, for example ZTC01 or $ZZCIP. ZTC01.
cpu
is a processor number from 0 to 15; for example 1.
$volume
is a disk volume name; for example $DATA.
entity
is a symbolic application entity name; for example SALES. Applications can be
represented as separate ASAP entities when they are defined using the ASAP
Entity Definition Language (EDL). Only LIST and REMOVE are applicable for
user-defined entities.
logical\
is a hierarchical, logical prefix that can be used to group and create aggregates
for files or processes. It can contain from one through four levels using the
backslash character as a level separator, depending on the entity and type of
domain name specified. For more information on using logical names, see
Section 5: File and Process Monitoring. SALES\ is an example of a logical
prefix.
$file
is a filename, subvolume name or filename pattern containing wild-card
characters in the subvolume or file portions of the name. For example,
$DATA.SUBVOL, $DATA.SUBVOL.FILE, $DATA.SUBVOL.F*, and
$DATA.SUB*.F*.
pathname
is a process object file or OSS file specified as an OSS pathname. OSS
pathnames must start with a slash character. For more information on
specifying OSS pathnames to ASAP, see Section 5: File and Process
Monitoring.
Note
Resolving the processes running from an OSS pathname can result in excessive low-
level messaging in the NonStop OS operating system. This method should be used
judiciously in extremely high-performance application environments.