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

Table 19 Summary of OSS Process Information (continued)
Number of ProcessesStarted ByDescription
File Name in
$SYSTEM.SYSnn
Process Name
1 per processorProcessor loadPipe serverOSSPS$ZPPnn
Supports the transfer of data between OSS processes that use pipes or FIFOs between processors. If this process
terminates abnormally it halts the processor in which it runs. For more information, see “Pipes and FIFOs” (page 39).
1 per processorProcessor loadOSP serverOSSSP$ZSPnn
Performs thread-aware OSS regular file operations on behalf of an application thread. Each OSP server (one per
processor) acquires shared OSS resources for operations without blocking threaded client applications from running
other threads. The OSP server also allows those shared OSS resources to be released without requiring involvement
of the client application when thread-aware I/O operations complete. If this process terminates abnormally it halts the
processor in which it runs. For more information, see “The OSS Server Process (OSP) Servers” (page 98).
1 per processorProcessor loadTransport agentOSSTA$ZTAnn
Manages OSS socket sessions for NonStop TCP/IP. When you use PTCP/IP or TCP/IPv6 this process is not used for
INET sockets other than to initiate the socket. Always used with AF_UNIX sockets. If this process terminates abnormally
it halts the processor in which it runs. For more information, see “Interprocess Communication Facilities” (page 35).
1 per processorProcessor loadResource agent serverOSSRA$ZRAnn
Beginning with the J06.14 and H06.25 RVUs, the OSS resource agent server provides current and peak usage
information for OSS File System resources to the OSS Monitor. There is one OSS resource agent server process for
each processor in your system. For more information, see “The OSS Resource Agent Servers” (page 93).
Multiple process pairs per
system
Processor loadTransport-providerTCPIP$ZTC0 or
$process-name
Default name for the transport-provider process for OSS AF_INET or AF_INET6 sockets when no other process name
is specified. Transport-provider processes can use any legal process name. For more information, see “Interprocess
Communication Facilities” (page 35).
1 per processorProcessor loadTerminal helperOSSTH$ZTTnn
Supports the select() and FILE_COMPLETE_() functions when used with OSS terminals. If this process terminates
abnormally it halts the processor in which it runs. For more information, see “Terminal Helper Servers” (page 33).
Multiple processes or
process pairs per system
$ZZKRN (recommended)
or operator command
OSSTTY processOSSTTY$process-name
An OSS terminal process that can redirect OSS standard files (stdin, stdout, stderr) to Guardian disk files, processes,
and terminals. You can start as many copies of OSSTTY as needed. Give each copy a unique process name. Other
than deciding how many copies of OSSTTY you need to run simultaneously, there are no management tasks associated
with OSSTTY. For more information, see “OSSTTY” (page 395).
Multiple processes per
system
operator commandTELNET server processTELSERV$process-name
The Telserv process is server portion of the TELNET protocol that supports virtual terminals. Runs over NonStop TCP/IP,
Parallel Library TCP/IP, or TCP/IPv6. Can be configured to run in the Guardian environment or the OSS environment.
A single Telserv process can support up to 256 virtual terminals. For more information, see the Telserv Manual.
410 Summary of OSS Processes