Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Internet-based connectivity and offers a more secure extension to inetd. For more details, see
“OSS Core Utilities User Commands” (page 243).
Obtaining Information About a Server
You can obtain the following information:
• Whether a server is running in the Guardian environment, as described in “Determining
Whether a Server Is Running” (page 130).
• The current configuration of an OSS name server, OSS sockets local server, OSS
message-queue server, or OSS transport-agent server, as described in “Determining the Current
Configuration of a Server” (page 131).
• Usage and configuration information for certain network services servers, as described in
“Determining Usage and Configuration of Network Services Servers” (page 132).
Determining Whether a Server Is Running
You can determine whether the following servers are running:
• A server used by the OSS environment but not administered through the OSS Monitor, as
described in “Checking Servers in the Guardian Environment That Are Not Administered
Through the OSS Monitor” (page 130).
• A server used by the OSS environment and administered through the OSS Monitor, as described
in “Checking Servers That Are Administered Through the OSS Monitor” (page 131).
• A server running in the OSS environment and not administered through an SCF interface, as
described in “Checking Servers That Run in the OSS Environment” (page 131).
Checking Servers in the Guardian Environment That Are Not Administered Through the OSS Monitor
To determine whether such a server is running, you use the basic SCF LISTDEV command. (There
is no OSS Monitor command to provide this information.)
Here is an example: Suppose you want to determine whether a transport-provider process for OSS
AF_INET sockets is running. The transport provider is the $ZTCn server, described under “OSS
Sockets” (page 39).
If you enter the LISTDEV command at an SCF prompt, a display similar to that shown in Example 8
(page 131) appears. In the figure, the transport-provider process $ZTC0 is shown as:
• Running, with:
Its primary process in processor 1 at PIN 47◦
◦ Its backup process in processor 0 at PIN 63
• Having a:
Logical device number of 228◦
◦ Device type of 48
◦ Device subtype of 0
◦ Scheduling priority of 180
• Using the object file \NODE1.$SYSTEM.SYS00.TCPIP
130 Managing Servers