ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 212 of 381
$process
is a process name, object filename or process name pattern containing wild-
card characters. For example, $ABC, $DATA.OBJECT.FILE and $AB*.
Note
Resolving the processes running from an object filename 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.
primary->backup
is the primary node name followed by "->" and the backup node name. No
spaces are allowed in the name, and the node names cannot contain the
leading backslash character. For example, NEWYORK->CHICAGO.
$supervisor
is the process name of the SPOOLER supervisor process for the SPOOLER
subsystem you want to monitor; for example, $SPLS.
$node
is a node name; for example, \NODE1.
$tape
is a tape device name; for example, $TAPE.
$tcpprocess
is the process name of a TCP/IP v4 process or a TCP/IPv6 Monitor process.
When you monitor a TCP/IP process you monitor the process
(TCPPROCESS) entity and all sub-entities that represent layers of it's
statistics. For example when you MONITOR TCPPROCESS $ZTCP0 you get
process stats for the TCPARP, TCPICMP, TCPICMP6, TCPIGMP, TCPIP,
TCPIP6, TCPLOOP, TCPMONGQ, TCPQIO, TCPRTE, TCPSOCK and
TCPUDP sub-entities. However you cannot monitor any sub-entities
exclusively using the monitor command. For example you cannot MONITOR
TCPARP $ZTCP0.
port
is a valid TCP/IP port number. You cannot monitor Ports that are managed by
TCP/IP processes that are not monitored. For example if you MONITOR
TCPPROCESS $ZTCP0 and then MONITOR TCPPORT 23 then ASAP will
only monitor connections on port 23 that are serviced by the $ZTCP0 process.