Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)
Monitoring OSS Processes From the Guardian Environment
The TACL STATUS command in the Guardian environment reports information about processes
running in the OSS environment:
• A STATUS command for an OSS process returns information about the pathname of the
executing program file and indicates that the process has an OSS process ID. For example,
the TACL command:
STATUS 4,354
would return a display similar to Example 4 when that process is the OSS shell. In the output,
the X to the left of the Guardian cpu,pin under “Process” indicates that the process has an
OSS process ID.
Example 4 TACL STATUS Display for an OSS Process
System \NODE1
Process Pri PFR %WT Userid Program file Hometerm
X 4,354 130 000 103,225 /bin/sh $ZTN0.#PTVNNP7
Swap File Name: $OSS001.#0
• A STATUS, DETAIL command provides more information in a different format. For example,
a STATUS *, DETAIL command could return information about a copy of an iTP WebServer
utility process among the rest of its output, as shown in Example 5 (page 63).
Example 5 TACL STATUS, DETAIL Display for an OSS Process
.
.
.
System: \NODE1 June 4, 2001 12:09
Pid: 9,326 ($Z0S5) Primary
Priority: 160
Wait State: %001 (LREQ)
Userid: 255,44 (SUPER.WEBMASTR)
Myterm: $ZTN1.#PT74DAB
Program File Name: $ROOT.ZYQ00000.Z00116NL
Swap File Name: $ROOT.#0
Process Time: 0:0:0.008
Process Creation Time: February 17, 2001 16:53:25.940213
Process States: RUNNABLE
GMOMJOBID:
OSS Pathname: /usr/tandem/webserver/applications/sis/_oss/bin/vtopic.pway
OSS Arguments: -configpath /usr/tandem/webserver/applications/sis/_oss/bin/inetsrch.ini
OSS PID: 24379404
.
.
.
The SCF PROCESS INFO and PROCESS STATUS commands for the NonStop Kernel subsystem
can provide information about persistent OSS processes. These commands work for:
• The OSS Monitor (see “Starting the OSS Monitor as a Persistent Process” (page 52))
• Any OSS server configured under the NonStop Kernel subsystem by OSS EasySetup (see
“EasySetup Utilities” (page 399))
• Any OSS application configured within the NonStop Kernel subsystem (see “Making OSS
Application Processes Persistent with the Kernel Subsystem” (page 64))
Monitoring OSS Processes 63